On Fri, Jul 25, 2003 at 02:42:35AM +0100, Toad wrote: > Various details have led us to the conclusion that NGRouting will not > work effectively unless we implement connection multiplexing first. > Proposal: > > New presentation protocol version representing MUXing mode. > > If we are in MUXing mode: > > 4 bytes - session identifier. Allocated by the sender, see below. > > 0 => message. Parse it, schedule it. > != 0 => trailing field chunk. The number identifies which one, since > we can have multiple trailing fields.
Actually, a slight modification: 0 = message 1 to MAXINT = trailing field chunk -1 = padding possibly -2 = data to send down to FnpLink layer e.g. IP address changes etc? -3 to -MAXINT = reserved for future use. > > 2 bytes - length of chunk. Included on BOTH trailing chunks and > messages - this makes accumulating and parsing easier. > > A message with a trailing field attached will contain an extra field > indicating the session identifier, but the message will be sent as a > message, and the trailing field will not start until the next chunk. > > > We will of course implement back compatibility for the current protocol. > > Comments? > -- > Matthew J Toseland - [EMAIL PROTECTED] > Freenet Project Official Codemonkey - http://freenetproject.org/ > ICTHUS - Nothing is impossible. Our Boss says so. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
pgp00000.pgp
Description: PGP signature
