I propose the addition of a few new FCP commands:
** GetLocalReference
In response, the node can say:
LocalReferenceResponse
<The node's local reference>
EndMessage
This will replace the current mechanism for obtaining a node's reference
which is to use the -x or --export command line option.
** TestReference
To get the node to "ping" a reference, the client sends a command in the
form:
TestReference
<a reference>
EndMessage
The node responds with either:
Success
time=<number: The length of time in miliseconds for the reference to
respond>
EndMessage
Or:
Failed
EndMessage
** GetReferencePool
In response, the node will send:
ReferencePoolResponse
Length=<number: number of bytes in trailing field>
Data
<@Length bytes of references whose nodes have a CP of 1>
This will be useful since it will allow a client to create a seed.ref
file which can be conveniently distributed via the web or email.
More ambitiously, by allowing FCP connections from a specific remote
host, that host could regularly harvest references from a variety of
volunteer servers around the net, and even use those servers in a
distributed way to test references using TestReference.
Comments?
Ian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20011007/db48a68d/attachment.pgp>
