> At 08:54 AM 3/9/04 -0700, Wiggins d Anconia wrote: > >In this case the desire to fork multiple processes and maintain > >bi-directional communication with them becomes a nightmare of dealing > >with forking code, pipes, and all of the other IPC nasties. > >POE::Wheel::Run encapsulates all of that providing a very simple > >interface for dealing with forking those processes and handling their > >input/output through events. So all of the pipe/select stuff gets > >hidden. Obviously there are some limitations of what you can do (aka > >real-time kind of loses some of its meaning) etc. but for the most part > >hiding the gory details is usually not a problem. The same can be said > >for TCP servers, and other types of daemons. > > So, it's a tool for managing a family of forked processes? It's primary > focus is IPC-related functionality? > >
Not exactly, that would be pigeon holing it. While it can handle those things very well, it is certainly not limited to them. It is easiest to think of it as a framework for handling time slicing, or event programming tasks, or multi-tasking processes. A good way to see what it is capable of is to check out the cookbook found here: http://poe.perl.org/?POE_Cookbook But realize that those are provided as documentation rather than as an exhaustive list of what it can do. There really isn't an exhaustive list of what it can do since it is a framework rather than any specific functionality. I was trying to come up with a good analogy but couldn't seem to find an appropriate one.... http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
