> > Simon Cozens rewrite of Advanced Perl Programming does have a POE
> > chapter - that's where I read about POE first.
>
> Seconded, Simon Cozens' book provides a nice introduction to POE. (As
> a side note, this book also contains one of the few usable
introductions
> to Unicode.)
Agreed. It
> On Thu, Mar 01, 2007 at 11:00:20PM -0800, David Davis wrote:
> > POE is not threaded, and therefore multiple 'event chains' won't be
> running
> > simultaneously in a single process.
>
> I think multiple event _chains_ *do* exist simultaneously. Just only
> one event _handler_ runs at a time. D
> i believe 'event chain' would be appropriate
>
> On 3/1/07, Michael Collins <[EMAIL PROTECTED]> wrote:
> >
> > POE Gang,
> >
> > I have a nomenclature question. Let's say you have one or more POE
> > sessions. When you have an
POE Gang,
I have a nomenclature question. Let's say you have one or more POE
sessions. When you have an 'event flow' - the flow of control moves
from session to session (or to different events within a session) - I'm
wondering what you call it. Is it a 'thread' or a 'threadoid'? Just
curious w
Here is a question I also posed on perlmonks.org...
(http://www.perlmonks.org/?node_id=601464)
I am searching for a way to catch and handle a Control-C when using
multiple POE sessions. I have successfully used the snippet from the POE
Cookbook to actually catch the INT signal in each of my Ses
