Pre-forking SOAP servers

[James Lavery]

Hi all,

Rob Riepel, in http://groups.google.com/[email protected]&rnum=2

indicates how to implement a forking SOAP server...

What I need to do is implement a pre-forking server - i.e. one which
forks of, say, 4 processes all listening on the same port.

I've already got this working for our own (in-house) tcp/ip non-SOAP
server processes (i.e. several listening on a port, and the first
picks up a request and processes it while the others continue to
listen), but we need to extend this so that they can handle SOAP
requests also/instead.

Any pointers would be greatly appreciated!

Thanks,

James

 

[Julian Scarfe]

What I need to do is implement a pre-forking server - i.e. one which
forks of, say, 4 processes all listening on the same port.

I've already got this working for our own (in-house) tcp/ip non-SOAP
server processes (i.e. several listening on a port, and the first
picks up a request and processes it while the others continue to
listen), but we need to extend this so that they can handle SOAP
requests also/instead.

Any pointers would be greatly appreciated!

Have you read Lincoln Stein's "Network Programming with Perl"? Although his
examples of pre-forking servers (Chapter 15) are HTTP not SOAP, the
principles may well be easily adaptable.

Julian Scarfe

 

[James Lavery]

Julian,
Thanks for the pointer - will look into it.

My problem is that I don't really want to have to dive deep into SOAP
etc., I'm hoping someone's managed to do this with existing Perl SOAP
packages (e.g. SOAP::Lite). The main issue is control over creation of
socket listeners etc.

Yes, this may be lazy, but according to some Perl gurus, laziness is a
virtue!

James