Ajax

I recently had the extreme pleasure to use node.js and socket.io on a project. Here are some insights. Objective So the objective of the project was to read data from the _changes feed of our CouchDB cluster (hosted by Cloudant) and publish the data to a widget which we can use to display a constant stream of “what are people doing right now”. The core of the problem we faced was not just taking this stream of data and feeding it on to a page, but since we’ll deploy this widget to our homepage we needed to make sure that no matter how many clients see it, the impact on the database cluster is minimal; for example, it would be a single client (or down the road up to three for failover) who actually read data from the cluster....

I know some of you out there are probably tired of jQuery and people raving about it’s goodness, but bare with me! Because jQuery never ceases to amaze me — especially when I haven’t looked at it — or client-side JavaScript code in general — in a good year or so. Refactoring I’ve been refactoring some of my old JavaScript libs on a project and I noticed that I had used evil eval() all over the place to parse the JSON from our API....