I have many systems with SOAP::Lite and prefer to use a standalone server (SOAP::Transport::(HTTP|TCP) because Fork on accept is a very bad option when you have many calls. Iīm prefer to use an single process with Listen is 10 or more, when one process is more quickly of ForkOnAccept!

I think PreFork is a good solution, but only now (after some years) my database are upgrading to transaction mode!

Pay attemption on timeouts on client side and a correct rollback actions (traped with SIGPIPE), or make an good "protocol" on client/server (Identify requests) if you need it.

I donīt check Net::Server at now, but I think itīs a great solution, because Iīm implementing Config, Log Facilities and requestor control by hand, and itīs very hard!

I don't like the idea of installing a web server to solve a problem that might be solved with perl itself :-)

I have an Config_Server and a Dist_Server with some Targets_Agents. At Config_Server I think are good point to use Apache&mod_perl, but never simultaneous without transaction database, for others perl solve all on *nix servers and MS plataform ;)