On Thu, Sep 20, 2001 at 04:57:44PM -0400, Dan Sugalski wrote: > >For clarification: do you mean async I/O, or non-blocking I/O? > > Async. When the interpreter issues a read, for example, it won't assume the > read completes immediately. That sounds like what I would call non-blocking I/O. Async I/O would involve syscalls like aio_read(). I'm being a bit pedantic here because I've been involved in heated debates in the past, which were resolved when the two sides realized that they were using different definitions of async I/O. :> - Damien
- RE: Parrot multithreading? Hong Zhang
- Re: Parrot multithreading? Rocco Caputo
- Re: Parrot multithreading? Dan Sugalski
- RE: Parrot multithreading? Dan Sugalski
- Re: Parrot multithreading? Damien Neil
- Re: Parrot multithreading? Dan Sugalski
- RE: Parrot multithreading? Hong Zhang
- Re: Parrot multithreading? Damien Neil
- Re: Parrot multithreading? Dan Sugalski
- Re: SV: Parrot multithreading? Michael L Maraist
- Re: SV: Parrot multithreading? Dan Sugalski
- RE: Parrot multithreading? Hong Zhang
- RE: SV: Parrot multithreading? Michael Maraist
- Re: SV: Parrot multithreading? Benjamin Stuhl
- Re: SV: Parrot multithreading? Dan Sugalski
- Re: SV: Parrot multithreading? Sam Tregar
- Re: SV: Parrot multithreading? Dan Sugalski