the problem is that both the client and the server waits for new line \n before they process the input.

Perhaps you could clarify this problem by showing us the actual behaviour and the expected behaviour of your programs.

You use the readline operator (<$sock>). By its very definition it waits for a newline (or EOF or error). You can avoid this by using read or sysread.

By the way, I don't think you need $| here. It only affects the current filehandle (STDOUT), whereas the line $sock->autoflush(1); makes the socket autoflushing. However, all sockets that were created with recent IO::Socket::INET versions have autoflush on by default. (But I don't know if Net::Server::PreFork uses that module.)

In reply to Re: Net::Server::PreFork requires new line to end input by betterworld
in thread Net::Server::PreFork requires new line to end input by yoop

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.