Hi there everyone! For the past 2 years I have maintained a library called nio4r which provides a cross-Ruby VM abstraction for I/O selectors which are the underpinnings of I/O selectors and reactors:
https://github.com/celluloid/nio4r This library supports at least MRI, JRuby, and Rubinius, and is highly influenced by the Java NIO design. The problem is I'm maintaining implementations for all of the popular Ruby VMs. I think it would be better if the API were standardized into core Ruby and each implementation could provide their own optimized implementation. There are changes I'd like to see happen before such a standardization occurs. However, I'd like to gauge interest about incorporating this sort of API into the core of the Ruby language itself before that happens. What do you all think about incorporating nio4r into Ruby itself? -- Tony Arcieri -- -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected] --- You received this message because you are subscribed to the Google Groups "rubinius-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
