README.md in jugglite-0.0.1.alpha vs README.md in jugglite-0.0.2.alpha

@@ -1,9 +1,11 @@
 # Jugglite
 
-Jugglite is a replacement for the incredible [Juggernaut](https://github.com/maccman/juggernaut) by Maccman. It uses [Server Sent Events](http://www.html5rocks.com/en/tutorials/eventsource/basics/) to push events from your application to the client's browser.
+[![Build Status](https://secure.travis-ci.org/andruby/jugglite.png?branch=master)](https://travis-ci.org/andruby/jugglite)
 
+Jugglite is a replacement for the incredible [Juggernaut](https://github.com/maccman/juggernaut) by Maccman. It uses [Server Sent Events](http://www.html5rocks.com/en/tutorials/eventsource/basics/) to push events from your application to the client's browser. It uses [Redis](http://www.redis.io) for publish/subscribe and [Thin](http://code.macournoyer.com/thin/) + [EventMachine](https://github.com/eventmachine/eventmachine) to run an evented server that can handle 10K+ concurrent connections.
+
 ## Installation
 
 Add this line to your application's Gemfile:
 
     gem 'jugglite'
@@ -14,19 +16,75 @@
 
 Or install it yourself as:
 
     $ gem install jugglite
 
-## Usage
+## Server Usage
 
+I use jugglite as rack middleware in development and as a standalone cluster in production behind nginx.
+
+### Stand-alone binary
+
 Jugglite comes with a binary. This binary runs a thin server that listens on redis for application messages and passes it along to all connected clients.
 
-You can run the binary from any terminal
-`jugglite`
+You can run the binary from any terminal like this (these options are the defaults):
 
-TODO: Foreman & multiple processes
+`jugglite --address 0.0.0.0 --port 3000 --max-conns 1024`
 
-TODO: Behind nginx so the client connects on one port
+### As rack middleware
+
+Add it to your `config.ru` file:
+`use Juglite::App, path: '/stream'` (use the `path` option )
+
+### As a cluster behind Nginx reverse proxy
+
+NOTE: because the html5 SSE implementation requires the connection to have the same hostname and port, you'll need to add a reverse proxy in front of your app and jugglite.
+
+TODO with Foreman?
+
+## Client Usage
+
+Use the browser's native [Server-Sent Events](http://www.html5rocks.com/en/tutorials/eventsource/basics/) implementation:
+
+```javascript
+  es = new EventSource('/stream?channel=yourchannelname');
+
+  es.addEventListener('message', function(e) {
+    // Do something with the data
+    console.log(e.data);
+    // If you JSON encoded the message
+    msg = jQuery.parseJSON(e.data);
+    }, false);
+
+  es.onopen = function(e) {
+    // Connection was opened.
+  };
+
+  es.onerror = function(e) {
+    if (e.readyState == EventSource.CLOSED) {
+      // Connection was closed.
+    } else {
+      // Some other error?
+    };
+  };
+```
+
+To support older browsers, use [Remy's](http://html5doctor.com/server-sent-events/) excellent [Pollyfill](https://github.com/remy/polyfills/blob/master/EventSource.js). It does revert to ajax long polling for browsers without a native EventSource implementation. Supports almost every old browser (even IE7).
+
+## Sending messages
+
+Use your favorite Redis client to simply publish messages to the channel your clients are subscribing to:
+
+```ruby
+redis = Redis.new
+redis.publish('yourchannelname', 'This is a message')
+# You may want to JSON encode your data
+redis.publish('yourchannelname', {hello: 'world', number: 47}.to_json)
+```
+
+## Performance
+
+It's been tested on a local machine with the `spec/benchmark/max_connections.rb` spec up to 16K concurrent connections.
 
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)