On Mon, Oct 08, 2001 at 12:11:17AM -0500, thelema wrote:
> > It certainly isn't nescessary, but I think it is useful, since it allows
> > a client to find out the node's reference easily, without having to know
> > where the node was installed.
> > 
> Why would the client want the noderef?  the reason you'd want a noderef
> would be to send it to someone, for seeding purposes, and an
> automatically created file would suffice quite nicely for that.

The question is whether it is preferable for someone to go around
hunting for a file on their hard disk, or to have that file served up to
them by their chosen user interface.  I think the latter is clearly more
sensible, and if so, providing this functionality in FCP is preferable.

> I agree the node should be left up, but you don't have to take down the
> node to use such a command-line parameter.  You don't even have to start
> a new one, just make the connection, attempt to auth, and then send the
> "disconnect" message.

I don't understand why you seem to want to avoid using FCP at all costs,
acting as an intermediary between the user and the node is exactly what
it was designed for. Sure, there are other ways to do it, the question
is which of them is better.

> > I did think about that too, but that would prevent the output from being
> > directly pipable into a seedNodes file, as an option it might be useful,
> > but I wouldn't make it a priority.  Lets worry about feature creep after
> > the basic functionality is implemented.
> I just want it as a diagnostics tool for looking at how my node is doing
> in terms of how successful it's been lately in contact other nodes.
> This CP-dump would definitely be seperate, and in addition to, the
> references dump for seeding purposes.

Actually, apparently we can embed the CP in the reference without
causing problems.

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/e03e780a/attachment.pgp>

Reply via email to