Haha, I got my own domain name wrong! Clearly it's been a long day... Link: http://ajax-gist.com/ http://ajax-gist.com/ In the end I built what was essentiall

Haha, I got my own domain name wrong! Clearly it's been a long day... Link: http://ajax-gist.com/ http://ajax-gist.com/ In the end I built what was essentially a proof-of-concept asynchronous Rails 3 application. The libraries I used under the hood to get everything async were: * Rack/Fiber-Pool: http://github.com/mperham/rack-fiber_pool http://github.com/mperham/rack-fiber_pool * EM Synchrony: http://github.com/igrigorik/em-synchrony http://github.com/igrigorik/em-synchrony * Eventmachine: http://rubyeventmachine.com/ http://rubyeventmachine.com/ Using Rails for what is essentially a thin proxy is overkill, and I could have gotten better performance with Node or by writing a Rack application directly. But I wanted to take the opportunity to get a handle on what would be involved with doing this in Rails, as not too many people have done it before that I am aware of (and at the time no-one had done it with Rails 3).