back to you on this but I will
From: Tony Wildish wild...@mail.cern.ch
Date: Thu, 7 May 2009 10:58:12 +0200
To: poe@perl.org
Subject: Re: Bug in PoCo::Child when PID wraps round (fwd)
Hi,
just checking one more time: is anyone looking after PoCo::Child,
or is
it orphaned?
TIA,
Tony
sorry, I still own it. I've just been disconnected from the world a long
time. it will take me a while to get back to you on this but I will
From: Tony Wildish wild...@mail.cern.ch
Date: Thu, 7 May 2009 10:58:12 +0200
To: poe@perl.org
Subject: Re: Bug in PoCo::Child when PID wraps round
Hi,
just checking one more time: is anyone looking after PoCo::Child, or is
it orphaned?
TIA,
Tony.
On Wed, 15 Apr 2009, Tony Wildish wrote:
Hi,
I sent this to the bug-poe-component-ch...@rt.cpan.org list some time ago
but it looks like that list is dead. Is there someone here
() calls aren't buffered in filters. They are however buffered in
the driver, and they're flushed
On Dec 14, 2006, at 10:26, Mike Schroeder wrote:
We have a POE app that reads multiple input files, reformats them
and the posts them to various binaries wrapped with PoCo::Child
that in turn load
We have a POE app that reads multiple input files, reformats them and
the posts them to various binaries wrapped with PoCo::Child that in turn
load the data into our underlying system. The problem we are running
into is that PoCo::Child seems to be buffering two or three records at a
time
wrapped with PoCo::Child that in turn
load the data into our underlying system. The problem we are running
into is that PoCo::Child seems to be buffering two or three records at a
time. Sometimes we have interdependencies between records going into
various loaders, so we need these to be unbuffered
with my apologies to everyone who has waited so long for this release,
version 1.39 of this module has just been posted to CPAN.
it fixes a number of issues, see the Changes file.
in the coming year I hope to have more time to devote to POE (at present I'm
working 60+ hrs/wk which leaves little
From: Mike Schroeder [EMAIL PROTECTED]
Organization: DonorWare LLC
Date: Tue, 14 Dec 2004 16:12:31 -0700
To: [EMAIL PROTECTED]
Subject: PoCo::Child
The PoCo::Child examples all use ls as the child program.
Mike, for examples of how to read/write, see the PoCo::Player components
e.g. Mp3
, I send a $c-quit(), (and checking the
process list the process is indeed gone), but something seems to be
hanging on -- POE won't wrap up and clean up after itself -- it just
hangs. I tried using PoCo::DebugShell, but PoCo::DebugShell and
PoCo::Child seem to fight over STDOUT:
this likely has
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
It didn't install for me:
ok 1 - use PoCo::Child
ok 2 - session created
ok 3 - read-only client started
ok 4 - got stdout
ok 5 - second instance
ok 6 - got stderr
ok 7 - done
ok 8 - hard callbacks
ok 9 - interactive client started
ok 10 - client write
ok 11 - quit tested
ok 12 - client restarted
: PoCo::Child
On Thu, 2002-09-19 at 00:49, Erick Calder wrote:
Rocco thought it'd be useful to have a component made out of
POE::Wheel::Run
so as to eliminate having to create an interim session just to receive
events from the wheel... so I've put one together under the name in the
subject header
12 matches
Mail list logo
