On Sunday 11 November 2001 18:58, Ian 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. Cleaner maybe. Easier no.
I wrote this as a quick debugging tool to help figure out what's going on with the CP's / routing. Adding ref harvesting was so easy and so useful that it seemed silly not to do it. But I never intended to write another standard node-client interface. I won't take offense if someone wants to write more generic FCP support for this functionality. --gj -- Freesites (0.3) freenet:MSK at SSK@enI8YFo3gj8UVh-Au0HpKMftf6QQAgE/homepage// (0.4) freenet:SSK at npfV5XQijFkF6sXZvuO0o~kG4wEPAgM/homepage// _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
