1. Always give multi-threading a try whenever you are thinking of fork.

    I am not saying you should never use fork, but look back at the history, one big reason that fork was/(unfortunately is) heavily used is that Perl did not support multi-thread (very well), which is getting improved from revision to revision.

    Breaking the old norms, and re-establish our norms on the new ground, especially for Perl newbies do not have a burden of history.

    Always look at both fork and multi-thread, make your decision on a case by case base.
  2. The other thing is that, taking fork and multi-thread as helper, not restriction. It is obvious that, you can archive what you want to do here without multi-thread or fork.

    Neither is it said that fork or multi-thread is a must, nor is it said that multi-thread or fork is the best. Look at the benefits that multi-thread and fork may give you, and make your design decision. Don't use those techniques, just because they are cool, and don't refuse to use them, just because they are a little bit more complex.

In reply to Re: Non-forked, bi-directional client/server by pg
in thread Non-forked, bi-directional client/server by Coruscate

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.