Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции GANJANET.LOCAL
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции GANJANET.LOCAL с датами от 13 Oct 05 22:03:42 до 05 Aug 17 10:35:42, всего сообщений: 3030
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1577 из 3030 =================================== GANJANET.LOCAL =
От   : Mithgol the Webmaster            2:5063/88          09 Nov 06 21:13:14
Кому : All                                                 09 Nov 06 21:13:14
Тема : [04/11] FIDOURL.TXT
FGHI : area://GANJANET.LOCAL?msgid=2:5063/88+b1c375d1
На   : area://GANJANET.LOCAL?msgid=2:5063/88+b1c375b5
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://GANJANET.LOCAL?msgid=2:5063/88+b1c37613
==============================================================================
Пpивет!

*** Также отослано в GANJANET.LOCAL
*** Также отослано в RU.FTN.WINSOFT
*** Также отослано в RU.FTN.DEVELOP
*** Также отослано в TITANIC.BEST

  * FIDOURL.TXT [■■■■■■■■■■■···················] [04/11] *

    The <scheme-specific-part> uses the reserved character "?"
    as the delimiter between required and optional part or URL:

    <scheme><scheme-delimiter><required-part>?<optional-part>

    The required part is REQUIRED. The optional part MAY be empty;
    if the optional part is empty, the "?" character before it MAY
    be omitted. If the optional part is empty and the "?" character
    is present, then the "?" character MUST be ignored.

    If the optional part is not empty, it consists of one or more
    "parameter=value" settings, delimited by the reserved "&"
    character as follows:

    <setting1>&<setting2>&<setting3>&<setting4>& ... &<settingN>

    However, the optional part MAY have the "&" character on URL's end
    as follows:

    <setting1>&<setting2>&<setting3>&<setting4>& ... &<settingN>&

    (in this case the last "&" character MUST be ignored).

    Each of these settings is expected to appear in "parameter=value"
    form:

    <parameter's name>=<parameter's value>

    If the value part is omitted, then the corresponding parameter
    is assigned an empty value. In this case the "=" character MAY
    also be omitted. Example of such an optional part of URL:

    subj=Test&path=&subscribe&to=Test+Robot

    In this example, parameters "path" and "subscribe" become empty,
    the parameter "subj" becomes equal to "Test" value, and the
    parameter "to" becomes equal to "Test Robot" value (because "+"
    represents the white space, see the corresponding section above).

    Parameters specified in the optional part of URL are also optional
    by nature. If a certain parameter does not appear in the given URL
    at all, it takes a default value; and default values for most of
    optional parameters are defined below, where the URL schemes are
    enumerated.

    The "parameter=value" pairs MAY have an arbitrary order
    of appearance in an optional part of URL.

    For example, this optional part of URL:

    to=Test+Robot&path=&subj=Test&subscribe

    is equivalent to the previous example.

    5.3.1. Dealing with inappropriate reserved characters
    -+---------------------------------------------------

      The reserved character "?" MUST be used only once in a URL; if
      there are many "?" in some URL, then the first appearance of "?"
      SHOULD be treated as the delimiter between required and optional
      parts of that URL, and the remaining "?" MAY be treated as if
      they were properly encoded ("%3F" character triplets), or even
      ignored.

      The reserved character "=" MUST be used only once in a parameter
      setting; if there are many "=" characters in some setting, then
      the first appearance of "=" SHOULD be treated as the delimiter
      between that parameter's name and the parameter's value; and
      the remaining "=" characters, encountered before the next "&"
      (or before URL's ending, if it's the rightmost "parameter=value"
      pair) MAY be treated as if they were properly encoded octets of
      that parameter's value ("%3D" triplets), or even ignored.

      "The first appearance" means the leftmost one, because
      it is natural to parse the scheme-specific part of URL
      in left-to-right order.

      The programs interpreting Fidonet URL MAY also stop the whole
      interpreting and ignore the rest of URL after the position where
      an inappropriate reserved character is first encountered. This
      behaviour is especially RECOMMENDED for the programs trying to
      isolate URLs from some plain text, where the white spaces and/or
      other delimiters before and after URLs tend to be sometimes
      omitted by chance.

6. Fidonet URL schemes designating actions
-+----------------------------------------

  The URL schemes enumerated below designate resources
  that are most often used in typical actions
  involving netmail or echomail composed and sent.

  According to the above section of delimiter guidelines,
  the ":" character (and not the "://" character triplet)
  SHOULD be used as the delimiter after <scheme> part of such URLs.

  6.1. "netmail:" scheme
  -+--------------------

    The "netmail:" scheme is used to designate the Fidonet netmail
    address of an individual or service. It uses standard Fidonet
    addressing notation, <zone>:<net>/<node>.<point>@<domain>
    (see FSP-1004 for details).

    The character "/" has its literal meaning for this scheme.

    The netmail URLs take the form:

    netmail:<zone>:<net>/<node>.<point>@<domain>?<optional-part>

    However, some parts of address ("<zone>:", "@<domain>"
    and/or ".<point>") MAY be omitted (see FSP-1004 for details).

    Examples:

       netmail:2:5030/1520.9>https://fido.g0x.ru/?netmail:2:5030/1520.9>netmail:2:5030/1520.9                           (point address)
       netmail:2:5063/88>https://fido.g0x.ru/?netmail:2:5063/88>netmail:2:5063/88                                (node address)
       netmail:182:5043/1@forestnet>https://fido.g0x.ru/?netmail:182:5043/1@forestnet>netmail:182:5043/1@forestnet     (node address outside of Fido)

    When a "netmail:" hyperlink is used (clicked, followed), a netmail
    composer software MAY be launched. With this possibility in mind,
    several optional parameters are designed for the "netmail:"
    URL scheme.

    6.1.1. Optional parameter "to"
    -+----------------------------

      The "to" optional parameter is used to designate the name of
      netmail addressee. Its default value MAY be "Sysop" or "SysOp".
      The default value MAY also be determined by some user setting
      of the netmail composer used to process the "netmail:" URL.

      Examples:

         netmail:2:5063/88?to=Mithgol+the+Webmaster>https://fido.g0x.ru/?netmail:2:5063/88?to=Mithgol+the+Webmaster>netmail:2:5063/88?to=Mithgol+the+Webmaster
         netmail:2:5030/1520.9?to=Trooper>https://fido.g0x.ru/?netmail:2:5030/1520.9?to=Trooper>netmail:2:5030/1520.9?to=Trooper
         netmail:2:50/13?to=Alex%20Kocharin>https://fido.g0x.ru/?netmail:2:50/13?to=Alex%20Kocharin>netmail:2:50/13?to=Alex%20Kocharin

    6.1.2. Optional parameter "subject"
    -+---------------------------------

      The "subject" optional parameter is used to designate
      the subject line of the netmail message composed. Its default
      value is empty; the default value MAY also be determined by
      some user setting of the netmail composer used to process
      the "netmail:" URL.

      Examples:

         netmail:2:5063/88?subject=Is+the+hypertext+Fidonet+ready%3F>https://fido.g0x.ru/?netmail:2:5063/88?subject=Is+the+hypertext+Fidonet+ready%3F>netmail:2:5063/88?subject=Is+the+hypertext+Fidonet+ready%3F

Пока!

--- Заповедал не зря милосердный Аллах по словам правоверных судить о делах!..
* Origin: Ты можешь ── но это не ускорит обретение тобою нирваны! (2:5063/88)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.032180 секунды