Child::IPC::Pipe - Pipe based IPC plugin for Child River stage two • 8 direct dependents • 20 total dependents

Creates 2 pipes just before forking....

EXODIST/Child-0.013 - 22 Jun 2016 15:23:05 GMT

Child::Link::IPC::Pipe - Base class for link objects used by the Child::IPC::Pipe plugin. River stage two • 8 direct dependents • 20 total dependents

EXODIST/Child-0.013 - 22 Jun 2016 15:23:05 GMT

Child::Link::IPC::Pipe::Proc - Proc object used by the pipe plugin. River stage two • 8 direct dependents • 20 total dependents

EXODIST/Child-0.013 - 22 Jun 2016 15:23:05 GMT

Child::Link::IPC::Pipe::Parent - Parent object used by the pipe plugin. River stage two • 8 direct dependents • 20 total dependents

EXODIST/Child-0.013 - 22 Jun 2016 15:23:05 GMT

Child - Object oriented simple interface to fork() River stage two • 8 direct dependents • 20 total dependents

Fork is too low level, and difficult to manage. Often people forget to exit at the end, reap their children, and check exit status. The problem is the low level functions provided to do these things. Throw in pipes for IPC and you just have a pile of...

EXODIST/Child-0.013 - 22 Jun 2016 15:23:05 GMT

Child::IPC::Pipely - use Child with IO::Pipely for more portable IPC River stage zero No dependents

Child is a great way to manage forking, but its default IPC uses "pipe" which sadly isn't as portable as it could be in places. IO::Pipely provides a better solution (and indeed describes the problem better than I can). Read more there....

JBERGER/Child-IPC-Pipely-0.01 - 24 Nov 2013 23:14:02 GMT

6 results (0.037 seconds)