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


Присутствуют сообщения из эхоконференции GANJANET.LOCAL с датами от 13 Oct 05 22:03:42 до 25 Nov 24 15:15:12, всего сообщений: 3031
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 1939 из 3031 =================================== GANJANET.LOCAL =
От   : Mithgol the Webmaster            2:5063/88          10 Feb 07 13:51:24
Кому : All                                                 10 Feb 07 13:51:24
Тема : [5/11] FidoURL.txt
FGHI : area://GANJANET.LOCAL?msgid=2:5063/88+45cda3f2
На   : area://GANJANET.LOCAL?msgid=2:5063/88+45cd9ef8
= Кодировка сообщения определена как: CP866 ==================================
==============================================================================
* изначально написано в эхоконференцию FTSC_PUBLIC
* также было отослано в эхоконференцию CU.TALK
* также было отослано в эхоконференцию GANJANET.LOCAL
* также было отослано в эхоконференцию RU.FIDO.WWW
* также было отослано в эхоконференцию RU.FIDONET.TODAY
* также было отослано в эхоконференцию RU.FTN.DEVELOP
* также было отослано в эхоконференцию SU.FIDOTECH
* также было отослано в эхоконференцию TITANIC.BEST

textsection 5 of 11 of file FidoURL.txt
textbegin.section

    6.1.5. Optional parameter "body"
    -+------------------------------

      The "body" optional parameter is used to designate the body part
      of the netmail message composed. (Its default value is empty.)
      The netmail composer MAY wrap the value of "body" parameter in
      elements of some user-defined message template (user-defined
      signature, greeting, etc.)

      Examples:

         netmail:2:5063/88?subj=About+FGHI&body=Fidonet+2.0+approached>https://fido.g0x.ru/?netmail:2:5063/88?subj=About+FGHI&body=Fidonet+2.0+approached>netmail:2:5063/88?subj=About+FGHI&body=Fidonet+2.0+approached
         netmail:2:50/0?subj=Complaint&body=That+sysop+is+so+annoying!>https://fido.g0x.ru/?netmail:2:50/0?subj=Complaint&body=That+sysop+is+so+annoying!>netmail:2:50/0?subj=Complaint&body=That+sysop+is+so+annoying!
         netmail:2:5030/1520.9?body=HellEd+needs+enormously+large+DLLs>https://fido.g0x.ru/?netmail:2:5030/1520.9?body=HellEd+needs+enormously+large+DLLs>netmail:2:5030/1520.9?body=HellEd+needs+enormously+large+DLLs

  6.2. "areafix:" scheme
  -+--------------------

    Areafixing letters is a special sort of netmail. Areafixing letter
    commands an uplink node (to which the letter is addressed and sent
    directly) to change some of its echomail subscription options. For
    example, the downlink (who writes the letter) may request itself
    to be subscribed and/or unsubscribed from certain echomail areas,
    order the rescan of message base, change packer/unpacker settings,
    view the list of echoes available, etc.

    An echomail area is a shared base of messages that have common
    areatag (area identifier) and are distributed through Fidonet
    via hierarchical and/or p2p-alike connections between individual
    Fidonet systems (nodes and points). See echomail specifications
    in FTS-0004.

    Areafixing letters usually follow a very strict scheme: they must
    have the downlink's password in subject line (in order for request
    to be properly authentified), and the name of a certain areafixing
    robot (e.g. "AreaFix", or "AreaMgr", or "AreaLink") must be given
    as the addressee name. All of these requirements are confidential
    by nature, and thus the above described "netmail:" scheme can not
    be used to design hyperlinks that invite to subscribe or to leave
    certain Fidonet echomail areas. A separate URL scheme is needed.

    The "areafix:" scheme is used to designate a Fidonet areafixing
    action that involves some echomail area.

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

    The areafix URLs takes the form:

    areafix:<areatag>?<optional-part>

    When "areafix:" hyperlink is used (clicked, followed), it SHOULD
    launch a netmail composer (or subscription manager) software that
    automatically composes the proper areafixing letter (addressed
    to an uplink node and ordering subscription to the given echomail
    area). However, it is RECOMMENDED that the software asks its user
    to confirm the ready subscription order or cancel it
    before that letter is sent.

    Examples:

       ...if you're a developer, subscribe via areafix:SU.FidoTech>https://fido.g0x.ru/?areafix:SU.FidoTech>areafix:SU.FidoTech
       and enjoy there an endless stream of FAQs...

       ...join today's Fidonet life discussions, use the hyperlink
       leading to areafix:Ru.Fidonet.Today>https://fido.g0x.ru/?areafix:Ru.Fidonet.Today>areafix:Ru.Fidonet.Today

    6.2.1. Optional parameter "uplink"
    -+--------------------------------

      Fidonet software usually has its own means to determine which
      uplink has the requested echomail area and would receive the
      areafixing netmail letter. However, if the system has several
      uplink nodes able to distribute the given echo, the "uplink"
      optional parameter MAY be used to recommend the preferred uplink
      node (provided that the author of the hyperlink has some reasons
      to recommend one uplink above all others).

      The "uplink" parameter takes a value that uses standard Fidonet
      addressing notation, <zone>:<net>/<node>.<point>@<domain>

      However, some parts of address ("<zone>:", "@<domain>"
      and/or ".<point>") MAY be omitted (see FSP-1004 for details).
      The point number is often omitted in the "uplink" parameter
      values, because Fidonet points almost never become uplinks.

      Examples:

         ...get the echo about embedded systems directly from its
         moderator, use areafix:Ru.Embedded?uplink=2:5029/32>https://fido.g0x.ru/?areafix:Ru.Embedded?uplink=2:5029/32>areafix:Ru.Embedded?uplink=2:5029/32

         ...those Titanic echoes never were on the backbone, use
         areafix:Titanic.PVT?uplink=2:5020/830>https://fido.g0x.ru/?areafix:Titanic.PVT?uplink=2:5020/830>areafix:Titanic.PVT?uplink=2:5020/830 and subscribe to one
         from the primary hub...

      The "uplink" parameter has no default value; the default
      behaviour of the subscription management software has to be
      determined by the network topology of uplink-downlink relations.

      Generally the software has nothing to do if an areafix URL
      designates an already subscribed echomail area. However, if
      the "uplink" optional parameter is present, the software MAY
      choose to cancel echomail subscription order formerly sent to
      the current uplink for the given echomail area, and then arrange
      for supply of the same echomail area from the preferred uplink
      provided by the value of the "uplink" parameter. (The user
      SHOULD be asked first whether such an action is appropriate.)

    6.2.2. Optional parameters "unsubscribe" and "leave"
    -+--------------------------------------------------

      If the "unsubscribe" optional parameter and/or its shorter
      synonym parameter "leave" appear in the areafix URL, then
      unsubscription from the given echomail area MUST be ordered
      instead of subscribing to that area.

      The value of these parameters is ignored; only their presence
      or absence determines the behaviour of the subscription manager.
      It is RECOMMENDED to assign an empty value to them, and to omit
      the "=" character, thus keeping areafix URL resonably short.

      Examples:

      areafix:Ru.PHP?unsubscribe>https://fido.g0x.ru/?areafix:Ru.PHP?unsubscribe>areafix:Ru.PHP?unsubscribe
      areafix:Ru.List.Citycat.Culture.Music.Announce.FantasyNews?leave>https://fido.g0x.ru/?areafix:Ru.List.Citycat.Culture.Music.Announce.FantasyNews?leave>areafix:Ru.List.Citycat.Culture.Music.Announce.FantasyNews?leave

    6.2.3. Future optional parameters
    -+-------------------------------

      Future versions of this document may introduce even more
      optional parameters for the areafix URLs, encouraging somewhat
      tighter control over rescan parameters, packer/unpacker settings
      and formats, etc.

      Programs interpreting areafix URLs SHOULD NOT be sure whether
      it is safe to ignore any of the unknown parameters. Some of
      future extensions may dramatically change the URL's meaning,
      as "unsubscribe" is already able to change it to the opposite.

      If an unknown parameter is encountered in the areafix URL,
      the user SHOULD always be asked whether it can be discarded
      safely enough.

textend.section


With best Fidonet 2.0 regards,
Mithgol the Webmaster.                 [Real nodelisted name: Sergey Sokoloff]

... 230. I will not procrastinate regarding any ritual granting immortality.
--- Just as the clouds have gone to sleep, Angels can be seen in heaven's keep
* Origin: I have a strange feeling, as if I already had a deja vu (2:5063/88)

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