This was fixed some time around 0.1202. Case closed. -- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org / poe.sourceforge.net On Tue, 20 Jul 1999 16:57:49 +0200 (CEST), Artur Bergman wrote: >On Tue, 20 Jul 1999, Rocco Caputo wrote: > >> On Mon, 19 Jul 1999 14:58:42 +0200 (CEST), Artur Bergman wrote: >> >> [sample code] >> > >> >I guess the best solution would for ReadWrite to croak if it found somone >> >else holding selects on the socket?. >> >> I think the best solution would be to allow multiple selects on >> the same filehandle, each mapping activity to a different state. >> That would support more than one wheel on the filehandle, which >> would allow for overlap while switching between wheels. >> >> This is hard to do, however, because wheels expect to do their own >> reading and writing. There would be a lot of confusion unless a >> "physical I/O" layer was interposed between wheels and the kernel. >> >> Croaking is a good work-around until a real solution can be >> implemented. > >How, and what use would there be to have several read and write selects? >If we add chained state dispatches that is solved. > >Artur
