Does anyone rely on I/O events arriving out of order? Right now they're dispatched without going through the queue, and it makes input flow control tricky.
I was thinking about changing the behavior, posting those events through the queue after all. This would also simplify multi-user chat and game servers that must synchronize data updates with user input (causes) and asynchronous events (effects). This change would also implicitly pause watchers while their input events are in the queue. That adds input flow control while preventing a ready filehandle from generating redundant input events. The change shouldn't break most programs, but I'd like to heard from people who think it may. Thanks. -- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net
