If there is indeed a child-parent relationship, there's no need for the pipes to be named. IPC::Open2 or IPC::Run spawns the child and provides unnamed pipes to it. (The child access the pipes as STDIN and STDOUT.) Using that module saves you the trouble of doing your own forking and of opening your own pipes.

That said, you can't use select on pipes in Windows, so pipes are quite useless. Without select (or threads), the parent could block waiting on one child while another child wishes to speak to the parent, or the parent could block waiting for output from a child while the child is waiting for input from the parent.

I recommend sockets instead. Using 'select' to handle multiple sockets provides an event loop, but I don't know how to integrate into Tk's event loop (having no Tk experience whatsoever).


In reply to Re: Named pipes on Win32 by ikegami
in thread Named pipes on Win32 by jdtoronto

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.