Matthew Toseland <[EMAIL PROTECTED]> writes: > The idea was to put everything on one port. The possible problem is > that public fproxy's should not allow access to NodeStatusServlet, > or the control page for the DistributionServlet, but we can fix this > with a config entry.
Another practical problem is that when you're having Mozilla downloading from freeenet, the "meta" pages will not be available as well. That's because Mozilla refuses to make more than N connections to the same host:port. Running administration tools on another port would work around this... And there is something to be said for having one port for users and another one for admins. -- Robbe
signature.ng
Description: PGP signature
