On Fri, Jun 22, 2001 at 11:42:32AM +0100, Theodore Hong wrote:
< >
> > Putting an API for Fred to call Servlets makes no sense because there is
> > no reason to be able to plug in arbritrary servlets into Fred, and
> > unless you want to turn Fred in a full fledged web server there never
> > was.
>
> I haven't looked at the servlet stuff, so I don't really have an opinion
> about whether it belongs, but I did have some intentions to turn fproxy
> into - not exactly a full web server, but a full proxy server. That is,
> all your normal HTTP requests as well as your Freenet requests would pass
> through fproxy. Then you would be able to catch anonymity-compromising
> stuff better, and you could do more rewriting on Freenet URL's.
The full HTTP specification is scary, and a proxy is the most
complicated implementation. I would really recommend that you go on a
hunt for a previously written http proxy if you do this.
> > OTOH, using servlets internally in fproxy to handle the HTTP requests
> > (parsing the HTTP request options into the servlet options) is a
> > different matter. If you did that, then the servlet part of fproxy could
> > plug into apache and other servers that run serverlets, which might be
> > useful - something that, unless I have misread the code gravely, could
> > not work today because the internals of fproxy expect to find HTTP
> > headers on the stream after the servlet is handled. That is internal to
> > fproxy however, such a servlet structure should not be visible to Fred's
> > core.
>
> That's another thought. However, I don't see how to reconcile this with an
> internal interface between fproxy and Fred. Either they communicate
> through shared memory, or they use sockets. If fproxy changes to use an
> internal interface, it is obviously no longer usable as an Apache servlet,
> unless you bring all of Fred into Apache as a servlet as well. (Although
> that might be an interesting possibliity too - imagine if every Apache
> webserver in the world came with Freenet by default.)
Ah, but you have missed the nice development when it comes to the
client. All the fproxy needs is to somehow receive a ClientFactory from
somewhere, and then it can act against the obtained clients the same
regardless of whether they are Internal Clients, external FNP clients,
or external FCP clients.
--
'DeCSS would be fine. Where is it?'
'Here,' Montag touched his head.
'Ah,' Granger smiled and nodded.
Oskar Sandberg
[EMAIL PROTECTED]
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
