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 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 ;)

--
Marco Antonio
Rio-PM

In reply to Re^2: Implementing a forking SOAP::Lite server by mda2
in thread Implementing a forking SOAP::Lite server by Tardis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.