README.md in celluloid-io-0.9.0 vs README.md in celluloid-io-0.10.0
- old
+ new
@@ -1,14 +1,14 @@
-
+
=============
-[](http://travis-ci.org/tarcieri/celluloid-io)
-[](https://gemnasium.com/tarcieri/celluloid-io)
+[](http://travis-ci.org/celluloid/celluloid-io)
+[](https://gemnasium.com/celluloid/celluloid-io)
You don't have to choose between threaded and evented IO! Celluloid::IO
provides an event-driven IO system for building fast, scalable network
applications that integrates directly with the
-[Celluloid actor library](https://github.com/tarcieri/celluloid), making it
+[Celluloid actor library](https://github.com/celluloid/celluloid), making it
easy to combine both threaded and evented concepts. Celluloid::IO is ideal for
servers which handle large numbers of mostly-idle connections, such as Websocket
servers or chat/messaging systems.
Celluloid::IO provides a different class of actor: one that's slightly slower
@@ -36,12 +36,14 @@
Like Celluloid::IO? [Join the Google Group](http://groups.google.com/group/celluloid-ruby)
Supported Platforms
-------------------
-Celluloid::IO works on Ruby 1.9.2+, JRuby 1.6 (in 1.9 mode), and Rubinius 2.0.
+Celluloid::IO requires Ruby 1.9 support on all Ruby VMs.
+Supported VMs are Ruby 1.9.3, JRuby 1.6, and Rubinius 2.0.
+
To use JRuby in 1.9 mode, you'll need to pass the "--1.9" command line option
to the JRuby executable, or set the "JRUBY_OPTS=--1.9" environment variable.
Usage
-----
@@ -83,11 +85,11 @@
```
The very first thing including *Celluloid::IO* does is also include the
*Celluloid* module, which promotes objects of this class to concurrent Celluloid
actors each running in their own thread. Before trying to use Celluloid::IO
-you may want to [familiarize yourself with Celluloid in general](https://github.com/tarcieri/celluloid/).
+you may want to [familiarize yourself with Celluloid in general](https://github.com/celluloid/celluloid/).
Celluloid actors can each be thought of as being event loops. Celluloid::IO actors
are heavier but have capabilities similar to other event loop-driven frameworks.
While this looks like a normal Ruby TCP server, there aren't any threads, so
you might expect this server can only handle one connection at a time.
@@ -112,11 +114,11 @@
first kicks off a background task for accepting connections on the server
socket, then kicks off a background task for each connection.
* __Reactor + Fibers:__ Celluloid::IO is a combination of Actor and Reactor
concepts. The blocking mechanism used by the mailboxes of Celluloid::IO
- actors is an [nio4r-powered reactor](https://github.com/tarcieri/celluloid-io/blob/master/lib/celluloid/io/reactor.rb).
+ actors is an [nio4r-powered reactor](https://github.com/celluloid/celluloid-io/blob/master/lib/celluloid/io/reactor.rb).
When the current task needs to make a blocking I/O call, it first makes
a non-blocking attempt, and if the socket isn't ready the current task
is suspended until the reactor detects the operation is ready and resumes
the suspended task.
@@ -147,10 +149,10 @@
* If I've accepted a patch, feel free to ask for a commit bit!
License
-------
-Copyright (c) 2011 Tony Arcieri. Distributed under the MIT License. See
+Copyright (c) 2012 Tony Arcieri. Distributed under the MIT License. See
LICENSE.txt for further details.
Contains code originally from the RubySpec project also under the MIT License
Copyright (c) 2008 Engine Yard, Inc. All rights reserved.