As far as I understand your concurrent I can provide the following answer.
The SOAP::Transport::HTTP::Daemon server builds upon HTTP::Daemon. The HTTP::Daemon documentation says This HTTP daemon does not fork(2) for you. Your application, i.e. the user of the HTTP::Daemon is responsible for forking if that is desirable.. So you need to fork.I do it this way: I have a single daemon but I use threads to process the request. Hence, the daemon is more or less immideately back for other clients.
In reply to Re: SOAP::Lite questions
by m-rau
in thread SOAP::Lite questions
by DJpumps
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |