I'd have to go dig into the library code again as I haven't been in there
since I did this myself a few months ago, but I believe you're correct. If
you inherit from ThreadingMixIn, it will create a new thread for each
incoming request. I believe it's the same way the standard
ThreadingTCPServer
Jeff McNeil wrote:
> This is off of memory so I apologize if I don't get all of the details right.
>
> The base SimpleXMLRPCServer uses TCPServer as it's server component
> and SimpleXMLXMLRPCRequestHandler as it's handler. The handler is a
> subclass of BaseHTTPRequestHandler, which itself doesn't
This is off of memory so I apologize if I don't get all of the details right.
The base SimpleXMLRPCServer uses TCPServer as it's server component
and SimpleXMLXMLRPCRequestHandler as it's handler. The handler is a
subclass of BaseHTTPRequestHandler, which itself doesn't handle any
multithreading.
"Achim Domma" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> is SimpleXMLRPCServer multithreaded or how does it handle multiple
> clients? I want to implement a simple server which will be queried by
> multiple processes for work to be done. The server will simply hold a
> q
I do it this way and it's always worked great for me.
SimpleXMLRPCServer is based on SocketServer, so you can use the ForkingMixIn
or ThreadingMixIn classe to create something to handle requests in
parallel.
from SocketServer import ThreadingMixIn
import SimpleXMLRPCServer
class ThreadedXMLRPCS
