On Mon, 19 Feb 2001, Adam Langley <agl at linuxpower.org> wrote:
> At the risk of seeming like we're just handing this down to you - we
> are just going to hand this down to you ;)
Thank you, Master, may I have another?
> A client opens a socket to a node. The transport is unencrypted and
> FNP format messages are exchanged.
It's probably best to leave transport details (like "...is
unencrypted") out of protocol specs. FCP over an encrypted connection
sounds like it might be a good idea at some point.
> ClientGet
> URI=<string: fully specified URI, such as freenet:KSK at test.html>
> HopsToLive=<number: HTL>
> End
[...]
> DataNotFound
> [Reason=<string: freeform>]
> EndMessage
[...]
> RouteNotFound
> [Reason=<string: freeform>]
> EndMessage
[...]
> DataFound
> DataLength=<number: number of bytes of metadata+data>
> [MetadataLength=<number: default=0: number of bytes of metadata>
> END
[...]
> Failed
> [Reason=<string: freeform>]
> End
What's up with the variations on the trailing field ("End",
"EndMessage", "END")?
Can a string as referred to above include a newline? I hope not...
-S
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://www.uprizer.com/mailman/listinfo/devl
