Yeah, all of them bring serious problems to the table, Coro supposedly segfaults in multitude of situations.

fork would be nice, but exchanging data between children, moving sockets between then (I have no idea if it's possible to pass SSL socket in any way...) etc is not a trivial task.

And managing a pool of processes is a tedious task, I already asked perlmonks about that,but there were no interesting answers (besides the usual POE fanboy fanfare).

Threads would be in randomly failing department, additionally there are way to many flavors, each with it's own set of problems, advantages and disadvantages.

Anyhoo, I don't need concurrency, if anything, I might use some form of cooperative multitasking, but it may be that there's no such solution outthere

In reply to Re^4: Splitting one large timeout into few smaller ones.. by Eyck
in thread Splitting one large timeout into few smaller ones.. by Eyck

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.