xml-rpc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Rall <...@finemaltcoding.com>
Subject Re: WebServer.java
Date Wed, 21 Aug 2002 18:45:33 GMT
"Andrew Evers" <andrew.evers@redwood.com> writes:

> If you embed the current XmlRpcServer as part of a servlet
> doPost() method, then there is a conflict between the threading
> done by the servlet engine, and that done by the XmlRpcServer.
> The servlet engine has already allocated a thread to the
> request, there is no need to pool and manage threads again.

It would be nice if one could get ahold of a single threaded object
which can process XML-RPC calls like XmlRpcServer can.  It would be
very cool if someone would factor that code out of XmlRpcServer.

> It seems to me that the current XmlRpcServer does a good job
> of handling threads in normal operation (without a servlet
> engine out front). If the Worker was split out, and passed
> an extra callback interface to handle the URI -> object mapping,
> then it would be easy to embed XML-RPC into an arbitary HTTP
> implementation without embedding either the XmlRpcServer
> or the WebServer.

Exactly.  Is anyone up to this job?
-- 

Daniel Rall <dlr@finemaltcoding.com>

Mime
View raw message