This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| # Usage: redis-cli publish message hello | |
| require 'sinatra' | |
| require 'redis' | |
| conns = [] | |
| get '/' do | |
| erb :index | |
| end |
| // Combine JS and CSS files | |
| // --- | |
| // | |
| // Make sure you install the npm dependencies | |
| // > cd YOUR_PROJECT_FOLDER | |
| // > npm install | |
| // | |
| // Than run: | |
| // > node build |
| var ED = ED || {}; | |
| // Utility functions | |
| ED.util = (function() { | |
| // Data structure functions | |
| function each(object, callback) { | |
| if (object === null) return; |
| // early experiments with node had mysterious double requests | |
| // turned out these were for the stoopid favicon | |
| // here's how to short-circuit those requests | |
| // and stop seeing 404 errors in your client console | |
| var http = require('http'); | |
| http.createServer(function (q, r) { | |
| // control for favicon |
| /* | |
| I've wrapped Makoto Matsumoto and Takuji Nishimura's code in a namespace | |
| so it's better encapsulated. Now you can have multiple random number generators | |
| and they won't stomp all over eachother's state. | |
| If you want to use this as a substitute for Math.random(), use the random() | |
| method like so: | |
| var m = new MersenneTwister(); |
