On Sun, Nov 11, 2001 at 03:58:51PM -0800, Ian Clarke wrote:
> On Sun, Nov 11, 2001 at 07:23:01PM -0500, Gianni Johansson wrote:
> > Look at Freenet.client.http.NodeStatusServlet
> >
> > You can set it up to allow remote connections on a per ip basis just like
> > fproxy.
> > e.g.
> > # freenet.conf fragment
> > nodestatus.class=Freenet.client.http.NodeStatusServlet
> > nodestatus.port=8889
> > nodestatus.allowedHosts=127.0.0.1,hawk.freenetproject.org
>
> This is cool. Not to look a gift horse in the mouth, but wouldn't it
> have been cleaner to implement this as a FCP command rather than opening
> up a new port? FCP was designed for just this kind of task, and we
> really shouldn't add a new listen-port for every new piece of
> node-client functionality.
I don't think node ref harvesting really falls under node-client
functionality. It's a rather special purpose (even scandalous ;)
undertaking that seems better suited to a servlet than an FCP command.
Freenet is above all a system of network protocols that we want to
be adopted outside the world of Fred, so to that end we ought to
keep FCP as simple as possible.
--
:: tavin cole (tcole at espnow.com) ::
if there's been a way to build it
there'll be a way to destroy it
things are not all that out of control
- stereolab
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
