Re: Asynchronous IO class or methods?

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous (in thread) N :the next article (the next thread) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

"Daniel Berger" <djberg96 / hotmail.com> schrieb im Newsbeitrag 
news:1107382523.162768.105890 / z14g2000cwz.googlegroups.com...
> Hi all,
>
> Are there any plans to add support for the POSIX functions aio_read,
> aio_write, aio_waitn and aio_cancel to the Ruby standard library?
>
> I thought perhaps an AIO (or perhaps NIO, ala Java) class would be
> worthwhile.  That or add methods to the existing IO class.
>
> Or is there no point in doing that?  Does io-reactor (RAA) already more
> or less accomplish the same goal?

My 0.02 EUR: I prefer to use threads for concurrent IO because that makes up 
for much simpler code.  Note also, that Ruby internally already uses 
nonblocking IO.

Kind regards

    robert