From: Yohanes Santoso <ysantoso-rubytalk@...>
Date: 2004-08-26T07:21:21+09:00
Subject: Re: Open Fifo for Writing

Scott Rubin <srubin@fsisys.com> writes:

> end?  One way I thought of was for the C process to send a message up
> the incoming fifo to the ruby process to tell it when the outfifo is
> ready for opening. But I just want to make sure there isn't an easier
> and slicker way to do it with ruby.

Another way would be to poll for writability.

Yet another way: looking at your example, the cprocess is started from
the rubyprocess and communication between the two ensue afterwards. I
can't tell for sure, but it seems the lifetime of the cprocess is
within the lifetime of the invoking rubyprocess. I also do not know if
using fifo is a requirement.

If using fifo is not a requirement, then you may consider using
socketpair (Socket#pair), the modern (arguably) way of setting up
two-way communication channel between parent-child processes.

YS.