> I think it's an interesting feature, but I don't use Wheel::Run enough
> to know how generally useful it is.  I'm looking for more discussion
> on it before making any decisions.

I think it's fairly useful.  I've implemented it in PoCo::Child but was
hoping to hear the other ideas Robert mentioned before releasing.

-----Original Message-----
From: Rocco Caputo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 8:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Feedback on POE::Wheel::Run changes


On Thu, Mar 06, 2003 at 11:00:26AM +1100, [EMAIL PROTECTED] wrote:
> I understand that there is a long-term goal to supercede POE::Wheel::Run
> with a component module with the tentative title of
POE::Component::Process
> (http://poe.perl.org/?V1.0-TODOS) and there has been a discussion on the
> mailing list previously about how the POE::Wheel::Run module could be
> improved.  In spite of this, or perhaps because of it, I have made some
> simple additions to the POE::Wheel::Run module which I have needed for
some
> in-house projects which I would like to get some feedback on.
>
> The first of these changes is a simple addition to include a Directory
> parameter to specific the location from within which the program specified
> is executed.  The diff for these changes against the CVS version of
> POE::Wheel::Run (version 1.44) is as follows:

[patch]

> Note that this creates a locally scoped directory change for execution and
> should not affect execution of other components and wheels.

I think it's an interesting feature, but I don't use Wheel::Run enough
to know how generally useful it is.  I'm looking for more discussion
on it before making any decisions.

> I also have changes for username and group specification with name rather
> than UID/GID, bute these changes are very minor and depends upon the
> getpwnam and getgrnam functions which may affect portability of the
change.
>
> Comments and feedback welcomed.

POE::Wheel::Run is already very UNportable.  We can probably work
around missing get(gr|pw)nam functions, or at least throw
"unsupported" errors wherever they fail.

-- Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/

Reply via email to