One issue with this approach is that the author is allowing users to start the background work, rather than putting it into a queue like he had been doing with his prior site. If his site gets slammed, this will be a problem, whereas with a queue he could set up his interface to let the user continue browsing the site while his/her work makes its way through the queue.<p>One nice find from the article is the link to the Flash implementation of websockets: <a href="http://github.com/gimite/web-socket-js" rel="nofollow">http://github.com/gimite/web-socket-js</a>
Why is switching from rb to js to get server side event-driven code better than using a rb library like EventMachine? Or is there another benefit of node.js that I didn't pick up?
Obligatory big ups to node:<p><a href="http://howtonode.org/" rel="nofollow">http://howtonode.org/</a><p><a href="http://wiki.github.com/ry/node/modules" rel="nofollow">http://wiki.github.com/ry/node/modules</a>