I'm now finally at the point where I'm detailing the behavior of each message type, and I want to make sure I understand the recently-changed details.
(1) "Depth" is gone now, right? I am assuming that replies just create their own HopsToLive value so that the replying node can't be identified from depth information. (2) Do Reply.Data, TimedOut, and RequestFailed need to copy SearchKey or any other header data from the request (other than HopsToLive and UniqueID)? I'm assuming not. (3) I am assuming that "Source" is always the immediate source of each message (i.e., the node sending this message, filled in by each node in transit), and that "DataSource" is not needed for anything by the protocol, but is optional, probably spoofed, and just a suggestion where to look for this data next time (and is deliberately spoofed on Inserts). (4) I was going to include the feature (not currently implemented as far as I know) that a node is allowed to record the address from which it receives any message and send further messages there if it wishes. Also, a Reply.Handshake can be sent by any node at any time to announce itself unrequested. (5) I'm making some brash assumptions about message names that you'll have to check when I post the spec. Please let me know now if someone has an objection to a particular naming scheme or any other thoughts on the matter. -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lcrocker.html> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
