The PoCo::Child examples all use ls as the child program. This is
fine for showing how to work with a child that wants some command line
arguments to generate STDOUT, but I need a solution that lets me write
to STDIN and respond to STDOUT. So I reworked the example to use nl
to accept some
I can see how you would frequently want to design states that could be
invoked in both blocking and non-blocking mode.
For example, imagine you had a session acting as a http client. You
might want to design the request() handler to work in both models:
1) [NON-BLOCKING] You could post a
On Tue, Dec 14, 2004 at 11:39:03AM -0800, Ofer Nave wrote:
I can see how you would frequently want to design states that could be
invoked in both blocking and non-blocking mode.
For example, imagine you had a session acting as a http client. You
might want to design the request() handler
