Extension URLs
Internally, AWeb uses an extension to the URL scheme for some tasks. You
can take advantage of this, by using the same URLs. These extension URLs
always start with "x-aweb:". Note that you should only
include such extension URLs in pages that will only be viewed by AWeb,
because other browsers will not recognize these URLs.
A good place for extension URLs would be your hotlist. You can, for
instance, access other hotlists from within your hotlist,
or even configure one of these as your
home page within AWeb.
Hotlists
AWeb uses extension URLs to identify its hotlist, and other browser's
hotlists.
x-aweb:hotlist
- Identifies AWeb's own hotlist.
x-aweb:amhotlist.rexx
- Identifies the ARexx based hotlist of AMosaic version 1.2. It uses the
file
ENV:mosaic/hotlist.html.
x-aweb:amhotlist.20
- Identifies the hierarchical hotlist of AMosaic 2.0 prerelease. It uses
the file
ENV:mosaic/.mosaic-hotlist-default.
x-aweb:ibhotlist/path
- Identifies other hierarchical hotlists, like other AWeb hotlists
or the format used by early prereleases of IBrowse.
Because this hotlist doesn't have a
fixed location, you must specify the full path and file name in the
URL.
Shell commands and ARexx macros
Two extension URLs exist to start shell commands or ARexx macros.
x-aweb:command/shell_command
- Forms the interface to start Shell commands.
x-aweb:rexx/ARexx_macro
- Forms the interface to start ARexx macros.
Miscellaneous
x-nil:
- A null URL. Clicking on a link to this URL, or loading an image with
this URL as source, does nothing. This can be useful to create "harmless"
examples.
Undocumented
URLs of the form x-aweb:mail/... and x-aweb:news/...
are intentionally undocumented. Never try and use these URLs directly.
Back to
index.