Your client uses fork which on Win32 is only an emulation that uses threads. The result is that instead of having two separate processes, you have a single process with two threads.

The means that the 'child' thread is in a wait state trying to read from the tcp port. At the same time, the 'parent' thread is trying to write to the same port. This doesn't work, at least not on Win32--YMMV on other platforms. The print will block until the port exits the read wait state, which it won't do until the server sends something. But the server won't send anything until the client succeeds in printing something.

The result is a classic deadlock.

The code was probably written for use on a POSIX platform where a real fork (and signals and...) are available from the OS. Such code does not port directly to Win32.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Windows TCP socket client hangs in perlipc code by BrowserUk
in thread Windows TCP socket client hangs in perlipc code by desiv

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.