Thanks for the advice. I think that we had decided yesterday to try 1)
since we don't know what we might be executing - it is not necessarily
Perl in the CHILD processes.
$Bill Luebkert wrote:
1) Use sockets with the children (a fair amount of coding).
2) Use files and poll the files for size changes (sloppy and not event driven).
3) Use shared memory (not a good choice since the only version is unsupported).
4) Do it all in the parent and forget the children (a matter of including
the child code into the daemon and where you would normally send a cmd to
the pipe, just call the child sub (make sure the child doesn't lock up
the task).
I would probably be tempted to use 4), but 1) should also be feasible.
In any case, I wouldn't use fork if children are involved (use Win32::Process).
--
Shane P. McCarron Phone: +1 763 786-8160 x120
Managing Director Fax: +1 763 786-8180
ApTest Minnesota Inet: [EMAIL PROTECTED]
_______________________________________________
ActivePerl mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
