On Sun, 07 Oct 2001, Ian Clarke wrote: > 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. > I think that the node's reference should be written to disk ad myref.ref or something when the node is automatically created. I don't think it's necessary (or that useful) to have this command.
> ** TestReference > > To get the node to "ping" a reference, the client sends a command in the > form: > > TestReference > <a reference> > EndMessage <SNIP> > I'm *VERY* for this functionality. This is something I've wanted for a long time. Instead of making it part of FCP, it'd be quite acceptable to have it be a command-line option where you pass the reference file, but I could code it up in liber2.pl to be able to do this, if we do it over FCP. > ** 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. > This is something that pretty much has to be done in FCP for it to be useful, because there is the functionality to dump the routing table right now, but you get a bunch of binary crap at the end for reasons only scipient knows. I might revise this so that instead of returning nodes whose CP=1, you could have a paremeter to the request to specify that you want references whose CP is greater than that number. That way you'd be able to get references which have been misbehaving, or even all references. Related to this would be a command that just dumps out (in some nice format) some info about each node (their contact info or whatever) and their CP, so we'd be able to look at the CPs for all neighbors. That'd be useful information for many reasons, and it'd have to be a FCP command. > 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. > Interesting. And possibly very useful. I like the idea. We just need someone with enough skillz to code it up. > Comments? > > Ian. Thelema -- E-mail: thelema314 at bigfoot.com If you love something, set it free. GPG 1536g/B9C5D1F7 fpr:075A A3F7 F70B 1397 345D A67E 70AA 820B A806 F95D -------------- 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/354b0e07/attachment.pgp>
