usefor-usepro-00 August 2004
[< Prev]
[TOC] [ Next >]
7.9.1. Duties of an Outgoing Gateway
From the perspective of Netnews, an outgoing gateway is just a
special type of reading agent. The exact nature of what the outgoing
gateway will need to do to articles depends on the medium to which
the articles are being gated. The operation of the outgoing gateway
is only subject to additional constraints in the presence of one or
more corresponding incoming gateways back from that medium to
Netnews, since this opens the possibility of loops.
In general, the following practices are recommended for all outgoing
gateways, regardless of whether there is known to be a related
incoming gateway, both as a precautionary measure and as a guideline
to quality of implementation.
1. The message identifier of the news article should be preserved if
at all possible, preferably as or within the corresponding unique
identifier of the other medium, but if not at least as a comment
in the message. This helps greatly with preventing loops.
2. The Date and Injection-Date of the news article should also be
preserved if possible, for similar reasons.
3. The message should be tagged in some way so as to prevent its
reinjection into Netnews. This may be impossible to do without
knowledge of potential incoming gateways, but it is better to try
to provide some indication even if not successful; at the least, a
human-readable indication that the article should not be gated
back to Netnews can help locate a human problem.
4. Netnews control messages should not be gated to another medium
unless they would somehow be meaningful in that medium.
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-13/Duties_of_an_Outgoing_Gateway.out May 2004
+++ ../usefor-usepro-00/Duties_of_an_Outgoing_Gateway.out August 2004
@@ -1,4 +1,4 @@
-8.8.1. Duties of an Outgoing Gateway
+7.9.1. Duties of an Outgoing Gateway
From the perspective of Netnews, an outgoing gateway is just a
special type of reading agent. The exact nature of what the outgoing