> At 11:08 PM 3/8/04 -0500, Wiggins d'Anconia wrote: > >This is where I do my usual little dance, though untimely as it may be > >in this case, across the stage and say "POE" then exit again as if I was > >still on vacation.... > > OK, I'll bite. What's so great about POE, and why, oh, why, do you love it > so? >
Well, that is a tough one. That is the problem with POE, steep learning curve. The reason why it is so great is that it allows you to take some of those things that "Perl makes possible" and turn them back into things that "Perl makes easy". 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. I love it because it made an application that was a major pain in the rear-end incredibly elegant and simple in a very short amount of time (aka after I got over the learning curve). 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>
