On Fri, May 04, 2001 at 02:35:30AM -0500, Brandon wrote: <> > > This is just the tip of the iceberg. If you read over this you get the > > idea that, "Hey there's a whole lot of completely unused baggage in here > > meant for the traditional HTTP web-application environment." Try looking > > at the other classes in Freenet.servlet -- it gets worse. > > We've gotten to the point that we are about to start implementing several > HTTP-based plugins. People have been talking about "extending" FProxy to > do things like insertion wizards and node control and configuration. This > is when we'll need the HTTP-specific capabilities of the servlet API. > Rather than cramming a lot of unrelated functionality into FProxy, the > proper approach is to write several HTTP servlets for the different > functions.
But then you need to load the Servlet AFTER the connection has been
