«

[Note: parts of this message were removed to make it a legal post.]

Github: https://github.com/tarcieri/cool.io
<https://github.com/tarcieri/cool.io>Rubygems:
https://rubygems.org/gems/cool.io

Cool.io (formerly known as Rev, and pronounced like Coolio of Gangster's
Paradise fame) is an event framework for Ruby built on libev, the same
library that provides high performance asynchronous I/O for Node.js. Cool.io
is great for building TCP clients and servers which handle large numbers of
connections and are primarily I/O bound. Cool.io also provides APIs for
filesystem monitoring. Cool.io is an alternative to EventMachine, albeit one
which using Ruby's own native I/O primitives rather than reinventing them,
and does as much as possible in Ruby instead of C, which should make it
easier for interested contributors to hack on.

Cool.io supports the following Ruby implementations:
- Ruby 1.8.6+
- Ruby 1.9.0+
- Rubinius HEAD

Cool.io includes backwards compatibility for Rev, so applications built
using Rev can depend on the cool.io gem but still "require 'rev'" and use
the Rev toplevel constant instead of Cool.io's cool new Cool.io "constant".
Backwards compatibility with Rev will be removed in a future release.

Support for building asynchronous HTTP servers with Cool.io is provided
through the Rainbows! asynchronous HTTP web server (based on Unicorn):
http://rainbows.rubyforge.org/

Changes (from Rev 0.3.2):
- Rename the project to cool.io
- Bump the version all the way to 0.9! Hell yeah! 1.0 soon!
- Rename the toplevel module from Rev to Coolio (with a cool Cool.io style)
- Backwards compatibility with Rev with deprecation warnings
- Use Jeweler to manage the gem
- Update to RSpec 2.0
- Update to libev 4.01
- Initial Rubinius support

--
Tony Arcieri
Medioh! A Kudelski Brand

Great news! I was concerned you'd moved on from Rev - very glad to see
this excellent library getting a new boost of life.

Thanks,
Sean

Tony Arcieri <> wrote:
> Changes (from Rev 0.3.2):
> - Rename the project to cool.io

What was the reasoning for this? I actually liked the Rev name

--
Eric Wong

[Note: parts of this message were removed to make it a legal post.]

On Fri, Nov 19, 2010 at 1:35 PM, Eric Wong <> wrote:

> What was the reasoning for this? I actually liked the Rev name
>

Cool.io is ever so slightly less ungooglable

--
Tony Arcieri
Medioh! A Kudelski Brand

[Note: parts of this message were removed to make it a legal post.]

On Fri, Nov 19, 2010 at 1:38 PM, Tony Arcieri <>wrote:

> Cool.io is ever so slightly less ungooglable
>

By the way Eric, while Cool.io has backwards compat for Rev, it'd be nice if
you could update Rainbows! to have "use :Coolio"

--
Tony Arcieri
Medioh! A Kudelski Brand

Cool beans... I've been wanting to try out Cool.io (well, Rev
actually) ever since I started using Twisted and EventMachine. Also, I
like your trickery for the Cool.io constant.

Quick question... any chance Cool.io works in JRuby?

On Tue, Nov 16, 2010 at 12:20 PM, Tony Arcieri <> wrote:
> Github: https://github.com/tarcieri/cool.io
> <https://github.com/tarcieri/cool.io>Rubygems:
> https://rubygems.org/gems/cool.io
>
> Cool.io (formerly known as Rev, and pronounced like Coolio of Gangster's
> Paradise fame) is an event framework for Ruby built on libev, the same
> library that provides high performance asynchronous I/O for Node.js. Cool.io
> is great for building TCP clients and servers which handle large numbers of
> connections and are primarily I/O bound. Cool.io also provides APIs for
> filesystem monitoring. Cool.io is an alternative to EventMachine, albeit one
> which using Ruby's own native I/O primitives rather than reinventing them,
> and does as much as possible in Ruby instead of C, which should make it
> easier for interested contributors to hack on.
>
> Cool.io supports the following Ruby implementations:
> - Ruby 1.8.6+
> - Ruby 1.9.0+
> - Rubinius HEAD
>
> Cool.io includes backwards compatibility for Rev, so applications built
> using Rev can depend on the cool.io gem but still "require 'rev'" and use
> the Rev toplevel constant instead of Cool.io's cool new Cool.io "constant".
> Backwards compatibility with Rev will be removed in a future release.
>
> Support for building asynchronous HTTP servers with Cool.io is provided
> through the Rainbows! asynchronous HTTP web server (based on Unicorn):
> http://rainbows.rubyforge.org/
>
> Changes (from Rev 0.3.2):
> - Rename the project to cool.io
> - Bump the version all the way to 0.9! Hell yeah! 1.0 soon!
> - Rename the toplevel module from Rev to Coolio (with a cool Cool.io style)
> - Backwards compatibility with Rev with deprecation warnings
> - Use Jeweler to manage the gem
> - Update to RSpec 2.0
> - Update to libev 4.01
> - Initial Rubinius support
>
> --
> Tony Arcieri
> Medioh! A Kudelski Brand
>

Tony Arcieri <> wrote:
> On Fri, Nov 19, 2010 at 1:38 PM, Tony Arcieri <>wrote:
> > Cool.io is ever so slightly less ungooglable

Heh.

> By the way Eric, while Cool.io has backwards compat for Rev, it'd be nice if
> you could update Rainbows! to have "use :Coolio"

Yes, it'll probably happen next week, there are a few other Rainbows!
things I've been slacking on.

--
Eric Wong

[Note: parts of this message were removed to make it a legal post.]

On Fri, Nov 19, 2010 at 3:39 PM, Bryan Richardson <> wrote:

> Also, I like your trickery for the Cool.io constant.
>

Thanks... although actually using Cool.io instead of Coolio adds an extra
method call so if you care about speed you probably shouldn't use it (at
least in the event loop itself)


> Quick question... any chance Cool.io works in JRuby?


Unfortunately no which is a bit sad because I do a lot of stuff with
JRuby. I've thought about writing a JRuby backend for it.

--
Tony Arcieri
Medioh! A Kudelski Brand

[Note: parts of this message were removed to make it a legal post.]

On Fri, Nov 19, 2010 at 3:42 PM, Eric Wong <> wrote:

> Yes, it'll probably happen next week, there are a few other Rainbows!
> things I've been slacking on.


Sweet. I wanted to present Rev/Revactor on Rainbows! at RubyConf but
couldn't find any examples to get me started (beyond use :Rev and use
:Revactor)

It'd be great if your Rainbows! documentation had a trivial example of
building an async HTTP request handler using Cool.io or Revactor.

--
Tony Arcieri
Medioh! A Kudelski Brand

Tony Arcieri <> wrote:
> On Fri, Nov 19, 2010 at 3:42 PM, Eric Wong <> wrote:
> > Yes, it'll probably happen next week, there are a few other Rainbows!
> > things I've been slacking on.
>
> Sweet. I wanted to present Rev/Revactor on Rainbows! at RubyConf but
> couldn't find any examples to get me started (beyond use :Rev and use
> :Revactor)
>
> It'd be great if your Rainbows! documentation had a trivial example of
> building an async HTTP request handler using Cool.io or Revactor.

Heh, I don't actually have much a clue what interests people when it
comes to async apps, I barely use the web myself.

I would imagine it's like writing any regular application with
Rev/Revactor, you could make async HTTP requests to other backends and
maybe some databases with adapters for them...

They're both pretty good for serving things with only local
dependencies (apps running off TokyoCabinet/SQLite/GDBM, etc)
and can maintain many idle client connections with keepalive.
(crank keepalive_timeout up from the default 5s).

--
Eric Wong