Hello

Both server implementations are a single process single thread implementations. They handle one connection at a time, waiting for input and echoing it back. Fork-related problems on the Win32 platform should not be the problem since fork is not used.

The comment about telnet running as another process is totally irrelevant since all programs mentioned were running as independent processes.

Different perl programs do not share the same process the way some browsers do. Every program is run as an independent process, and just because one perl program is blocking does not mean all perl programs would block.

Aziz,,,

In reply to Re: Re: IO::Socket vs. Socket vs. off-the-shelf telnet by abstracts
in thread IO::Socket vs. Socket vs. off-the-shelf telnet by adamsj

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.