It sounds like the key is to get your reading and your parsing/logic separated. Once that is done, you can easily swap out different reading methods and see what works best.

One way to do it single threaded is to put socket/buffer pairs into a hash, and call a function to fill those buffers. Once one of the buffers gets to a usable point (such as containing a newline), you can split/regex/substr it off the buffer and do what needs doing.

Your filler function can dump all the sockets into a select and see which ones can be read. Read (once!) only those that are readable, and append to the associated buffer.
Returning a list of only the socket (keys) which changed during that read cycle might be handy to save CPU.

In reply to Re: non-blocking socket client? by SuicideJunkie
in thread non-blocking socket client? by ethrbunny

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.