Now you've got me wanting IO::Pipe::Interdimensional.

Threads are way better than processes if you can use them effectively, as you can share data instantly. As long as you're careful about locking everything down, it's fine. BeOS was a great introduction to how massive multi-threading can be a Good Thing.

The only unfortunate part about mod_perl is that 2.0 isn't "threaded" so much as "thread aware". Maybe the Perl 6 mod_perl will fix this and life will be Good. One of my biggest grumbles about mod_perl is that you have all these processes with exactly the same data, and no easy way to share it. IPC::Shareable is only so good.

In reply to Re: To thread or not to thread by tadman
in thread To thread or not to thread by hagus

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.