Text 666, 264 rader
Skriven 2007-02-10 13:53:59 av Mithgol the Webmaster (2:5063/88)
Ärende: [11/11] FidoURL.txt
===========================
* written in FTSC_PUBLIC
* also sent to CU.TALK
* also sent to GANJANET.LOCAL
* also sent to RU.FIDO.WWW
* also sent to RU.FIDONET.TODAY
* also sent to RU.FTN.DEVELOP
* also sent to SU.FIDOTECH
* also sent to TITANIC.BEST
textsection 11 of 11 of file FidoURL.txt
textbegin.section
7.3. "faqserv://" scheme
-+----------------------
FAQ servers are Fidonet stations that accept special requests
containing file names (or aliases) of certain texts. Such requests
are sent via Fidonet netmail. The FAQ server processes the request
and sends the requested text to the sender of request; the text is
sent via Fidonet netmail in a single letter (as a whole)
or in several letters (in sections).
The faqserv URLs take the form:
faqserv://<server>/<request>/<object-path>?<optional-part>
The character "/" has its literal meaning in the <optional-part>
of URLs of this scheme. The character "/" has its reserved meaning
in the required part of URL (<server>/<request>/<object-path>),
playing the role of delimiter between parts of the path. However,
inside <server> part the character "/" again MUST have its literal
meaning and MUST appear once (and only once!) as the delimiter
between parts of the server address.
The <server> part of a faqserv URL MUST be present. The standard
Fidonet addressing notation, <zone>:<net>/<node>.<point>@<domain>
(see FSP-1004 for details), is used in <server> address. However,
some parts of address ("<zone>:", "@<domain>" and/or ".<point>")
MAY be omitted (again, see FSP-1004 for details). The <server>
part of a faqserv URL specifies the Fidonet address of the station
(the FAQ server) which is implied to be queried.
If the <object-path> of a faqserv URL is not empty, then
its <object-name> MUST also be non-empty by definition, and
it specifies the name of an object embedded in the netmail text
of the response sent by that FAQ server. Either that object
or some of its inner parts, according to <object-path>, is
designated.
However, the netmail response messages MAY contain more than one
object of the same name. In this case the designated object is
the latest one among only those which are known how to decode
them. See section 7.2.2.2 for the details of what object is
considered the latest.
The <request> part of a faqserv URL is either empty, or not empty,
or not present at all. These are three separate possible cases.
If the <request> part of a faqserv URL is present but empty,
the slashes around it MUST not be omitted. Such an URL implies
a default request to the given server. This MAY be a request
for help (i.e. "HELP" request), a request for the list of topics
(e.g. "%LIST" request), or any other request probably determined
by some user settings or contents of a database of FAQ servers.
Examples:
faqserv://2:5020/1641.7//
The list of FAQServer topics is requested.
faqserv://2:5030/1410.100//sample.zip
ZIP file is located inside the standard response.
If the <request> part of a faqserv URL is not present at all, then
the <object-path> MUST also be empty and "<request>/<object-path>"
MUST be omitted entirely, and the preceding "/" character MAY also
be omitted. In this case the faqserv URL designates the FAQ server
itself, as a Fidonet system. Such an URL MAY designate an action
and not a resource; for example, it may designate adding the given
FAQ server to some list or to a database of FAQ servers.
Examples:
faqserv://2:5043/17.100@fidonet/
faqserv://2:5054/80.999
If the <request> part of a faqserv URL is not empty, it specifies
the request to be sent to the given server. The URL designates
either the response as a whole (if the <object-path> is empty),
or just an object inside the response (if the <object-path> is
not empty).
Examples:
faqserv://2:5054/83/ELINE/blath/Feainnewedd (an object)
faqserv://2:5054/83/TNT (<object-path> is empty)
faqserv://2:5054/83/TNT_FAQ/ (<object-path> is empty)
If the <request> part of a faqserv URL is present, then receiving
a message (or several messages) via netmail is implied. However,
most of the auxiliary technical and decorative elements of netmail
(i.e. taglines, tearlines, origin lines, greeting lines, signature
lines, etc.) SHOULD be stripped from the response text when the
netmail is received and the response is extracted from it. It is
useful to remember that the response MAY span several messages,
and sections of it SHOULD be stripped of all their wrappings
before they are finally combined.
If is possible for resources designated by faqserv URLs to appear
as elements of complex data structures (e.g. as objects on pages
of hypertext). Fidonet browsers SHOULD cache the extracted objects
and/or raw netmail response letters to allow immediate rendering
of the resources already requested before.
7.3.1. Optional parameter "bot"
-+-----------------------------
Sometimes the FAQ server station does not respond to the request
that is not addressed to a certain name of the service robot.
Such a behaviour is especially natural for stations where the
same <zone>:<net>/<node>.<point>@<domain> address is shared by
both human and automatic addressees, or where several bots exist
(e.g. a FAQ robot and an areafixing robot).
In such cases the "bot" optional parameter is appended to the
faqserv URL. The value of the "bot" optional parameter specifies
the name of the necessary addressee; it MUST be copied verbatim
to the corresponding message field of the netmail request.
7.3.2. Future optional parameters
-+-------------------------------
Future versions of this document may introduce even more
optional parameters for faqserv URLs, encouraging somewhat
tighter control how the request is sent (e.g. whether the
<request> part of the URL is copied to the subject line
of netmail or to the message body).
7.4. "fecho://" scheme
-+--------------------
Fidonet file echoes are somewhat similar to the echomail areas
in the terms of transport and distribution. However, files are
broadcast there instead of messages. File echo is a shared base
of files that have common areatag (file echo identifier) and are
distributed through Fidonet via hierarchical and/or p2p-alike
connections between individual Fidonet systems (nodes and points).
The fecho URLs take the form:
fecho://<areatag>/<object-path>?<optional-part>
The character "/" has its literal meaning in the <optional-part>
of URLs of this scheme. The character "/" has its reserved meaning
in the required part of URL (<areatag>/<object-path>), playing
the role of delimiter between parts of the path. If an <areatag>
contains the character "/" in its literal meaning, the character
MUST be encoded.
If the <object-path> part is empty, the fecho URL designates the
file echo as a whole.
Examples:
fecho://aftnbinkd
fecho://XOFCELIST/
If the <object-path> of a fecho URL is not empty, then
its <object-name> MUST also be non-empty by definition,
and it specifies the name of a file that is available
as a result of a broadcast though the given file echo.
Examples:
fecho://aftnmisc/HATCHDIR.RAR
fecho://aftnged/RUGEDFAQ.RAR/gedplus.faq
fecho://FIDONEWS/FNEWSK19.ZIP/
fecho://aftnbinkd/BNDMAN.ZIP/man/gif/
If an <areatag> corresponds to a file echo which is not available
on the system, then the designated resource is not available.
The user MAY be asked whether he wants to subscribe to that echo.
An FTP mirror of the file echo MAY also be used, if an Internet
connection to such a mirror is available.
7.5. "freq://" scheme
-+--------------------
It is possible for Fidonet stations to request files directly
from each other; there is even a protocol of distributed
file requests, proposed in FSC-0071.
The freq URLs take the form:
freq://<server>/<object-path>?<optional-part>
The character "/" has its literal meaning in the <optional-part>
of URLs of this scheme. The character "/" has its reserved meaning
in the required part of URL (<server>/<object-path>), playing
the role of delimiter between parts of the path. However, inside
the <server> part the character "/" again MUST have its literal
meaning and MUST appear once (and only once!) as the delimiter
between parts of the server address.
The <server> part of a freq URL MUST be present. The standard
Fidonet addressing notation, <zone>:<net>/<node>.<point>@<domain>
(see FSP-1004 for details), is used in <server> address. However,
some parts of address ("<zone>:", "@<domain>" and/or ".<point>")
MAY be omitted (again, see FSP-1004 for details). The <server>
part of a freq URL specifies the Fidonet address of the station
that will provide the requested file.
If the <object-path> is empty, the freq URL designates the station
itself, as a Fidonet system able to provide files by request.
If the <object-path> of a faqserv URL is not empty, then
its <object-name> MUST also be non-empty by definition, and
it specifies the name of a file that is requested from the remote
Fidonet station specified by the <server> part of the URL. The URL
designated either the file itself or one of inner part of the file
(according to the structure of the <object-path> part of the URL).
If is possible for resources designated by freq URLs to appear
as elements of complex data structures (e.g. as objects on pages
of hypertext). Fidonet browsers SHOULD cache the requested files
when they are received, in order to allow immediate rendering of
the resources already requested before.
7.5.1. Future optional parameters
-+-------------------------------
Future versions of this document may introduce even more
optional parameters for freq URLs, encouraging somewhat
tighter control how the file is requested. For example, some
Fidonet stations MAY deny or delay file requests that are sent
in a certain inappropriate time of the day, or day of the week;
so a parameter or two MAY appear to specify the time and the
week day when the file request is relatively safe.
Programs interpreting freq URLs SHOULD NOT be sure whether
it is safe to ignore any of the unknown parameters. Some of
future extensions may dramatically change the probability
of the success of a file request, especially when such
a parameter controls the file request time.
If an unknown parameter is encountered in the freq URL,
the user SHOULD always be asked whether it can be discarded
safely enough.
**********************************************************************
EOTD END OF THE DOCUMENT
**********************************************************************
textend.all
With best Fidonet 2.0 regards,
Mithgol the Webmaster. [Real nodelisted name: Sergey Sokoloff]
... 6. I will not gloat over my enemies' predicament before killing them.
--- Something is rotten in the state of Denmark. (Shakespeare, Hamlet, I, IV)
* Origin: Be careful, the paranoid ones are always wathing you!.. (2:5063/88)
|