From: minima Date: Fri, 20 Aug 2004 11:52:56 +0000 (+0000) Subject: add groff to makefile X-Git-Tag: R_1_51B~8 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=6c8062c1356fe49974da2df121852b41971f7b77;p=spider.git add groff to makefile more detail changes --- diff --git a/techdoc/Makefile b/techdoc/Makefile index 68d231b5..3aa05137 100644 --- a/techdoc/Makefile +++ b/techdoc/Makefile @@ -2,3 +2,4 @@ protocol.1 : protocol.pod podchecker protocol.pod pod2man protocol.pod > protocol.1 pod2html protocol.pod > protocol.html + groff -mandoc protocol.1 | ps2pdf - protocol.pdf diff --git a/techdoc/protocol.pod b/techdoc/protocol.pod index 5ea94c66..6a56b638 100644 --- a/techdoc/protocol.pod +++ b/techdoc/protocol.pod @@ -31,20 +31,38 @@ for inter-node communications. =head1 DESCRIPTION -This protocol is encoded in UTF8 with HTTP style escaping. It is +This protocol is designed to be an extensible basis for any type of one to many "instant" line-based communications tasks. This protocol is designed to be flood routed in a meshed network in -as efficient a manner as possible. +as efficient a manner as possible. The reason we have chosen this +mechanism is that most L need to be broadcast to all nodes. + +Experience has shown that nodes will appear and (more infrequently) +disappear without much (or any) notice. +Therefore, the constantly changing and uncoordinated +nature of the network doesn't lend itself to fixed routing policies. + +Having said that: directed routing is available where routes have +been learned through past traffic. +Those L that could be routed (mainly single line one to +one "talk" L) +happen sufficiently infrequently that, should they need to be flood routed +(because no route has been learned yet) it is a small cost overall. + +=head1 Messages + +A message is a single line of UTF8 encoded and HTTP escaped text +terminated in the standard internet manner with a . Each message consists of a L and a L. -The two sections are separated with the '|' character and the whole -message is terminated in the standard RFC/Internet manner with the -ascii characters. It follows that these -characters (as well as a small number of other reserved characters) +The two sections are separated with the '|' character. +It follows that these +characters (as well as non-printable characters, , and +a small number of other reserved characters) can only be sent escaped. This is described further in the -L. +L and L. Most of this document is concerned with the L, however some L which all implementation should issue and @@ -58,7 +76,7 @@ effectively a datagram. It is assumed that nodes are connected to each other using a "reliable" streaming protocol such as TCP/IP or -AX25. Having said that: in context, messages in this protocol could be +AX25. Having said that: in context, L in this protocol could be multi/broadcast, either "as is" or wrapped in some other framing protocol. @@ -67,10 +85,10 @@ through your node" protocol, there is no guarantee that a message will get to the other side of a mesh of nodes. There may be a discontinuity either caused by outage or deliberate filtering. -However, as it is envisaged that most messages will be flood routed or, -in the case of directed messages (those that have L and/or +However, as it is envisaged that most L will be flood routed or, +in the case of directed L (those that have L and/or L fields) down some/most/all interfaces showing a route for that -direction, it is unlikely that messages will be lost in practice. +direction, it is unlikely that L will be lost in practice. =head2 Field Description @@ -137,7 +155,7 @@ neighbouring nodes must increment this field before passing it on to higher layers for onward processing. Implementations may have an upper limit to this field and may -silently drop incoming messages with a L count greater than the +silently drop incoming L with a L count greater than the limit. =item B @@ -223,7 +241,7 @@ tuple. The basic system will learn which interfaces can see what nodes by looking at the tuple and merging that with the L count. Each interface remembers the latest L with the lowest L for each L that arrives on that interface. It also remembers -the number of messages for that L that has been received on +the number of L for that L that has been received on that interface. Any message for onward broadcast is duplicated and sent out on all @@ -341,7 +359,7 @@ are written according to this specification must say: use UTF8; A message (or line) is terminated with -0x0d 0x0a. Incoming messages must be accepted even when terminated +0x0d 0x0a. Incoming L must be accepted even when terminated with just . Care must be taken to make sure that fields have any reserved characters