redis 0.6.7 → 0.7.3

package/.npmignore

@@ -0,0 +1 @@
+node_modules

package/README.md

@@ -8,7 +8,7 @@ experimental Redis server branches.
 Install with:
 
     npm install redis
-    
+
 Pieter Noordhuis has provided a binding to the official `hiredis` C library, which is non-blocking and fast.  To use `hiredis`, do:
 
     npm install hiredis redis
@@ -23,9 +23,13 @@ happen between node and native code modules after a node upgrade.
 
 Simple example, included as `examples/simple.js`:
 
+```js
     var redis = require("redis"),
         client = redis.createClient();
 
+    // if you'd like to select database 3, instead of 0 (default), call
+    // client.select(3, function() { /* ... */ });
+
     client.on("error", function (err) {
         console.log("Error " + err);
     });
@@ -40,6 +44,7 @@ Simple example, included as `examples/simple.js`:
         });
         client.quit();
     });
+```
 
 This will display:
 
@@ -50,7 +55,7 @@ This will display:
     2 replies:
         0: hashtest 1
         1: hashtest 2
-    mjr:~/work/node_redis (master)$ 
+    mjr:~/work/node_redis (master)$
 
 
 ## Performance
@@ -84,7 +89,7 @@ The performance of `node_redis` improves dramatically with pipelining, which hap
 ### Sending Commands
 
 Each Redis command is exposed as a function on the `client` object.
-All functions take either take either an `args` Array plus optional `callback` Function or
+All functions take either an `args` Array plus optional `callback` Function or
 a variable number of individual arguments followed by an optional callback.
 Here is an example of passing an array of arguments and a callback:
 
@@ -93,18 +98,25 @@ Here is an example of passing an array of arguments and a callback:
 Here is that same call in the second style:
 
     client.mset("test keys 1", "test val 1", "test keys 2", "test val 2", function (err, res) {});
-    
+
 Note that in either form the `callback` is optional:
 
     client.set("some key", "some val");
     client.set(["some other key", "some val"]);
 
+If the key is missing, reply will be null (probably):
+
+    client.get("missingkey", function(err, reply) {
+        // reply is null when the key is missing
+        console.log(reply);
+    });
+
 For a list of Redis commands, see [Redis Command Reference](http://redis.io/commands)
 
 The commands can be specified in uppercase or lowercase for convenience.  `client.get()` is the same as `client.GET()`.
 
-Minimal parsing is done on the replies.  Commands that return a single line reply return JavaScript Strings, 
-integer replies return JavaScript Numbers, "bulk" replies return node Buffers, and "multi bulk" replies return a 
+Minimal parsing is done on the replies.  Commands that return a single line reply return JavaScript Strings,
+integer replies return JavaScript Numbers, "bulk" replies return node Buffers, and "multi bulk" replies return a
 JavaScript Array of node Buffers.  `HGETALL` returns an Object with Buffers keyed by the hash keys.
 
 # API
@@ -115,8 +127,8 @@ JavaScript Array of node Buffers.  `HGETALL` returns an Object with Buffers keye
 
 ### "ready"
 
-`client` will emit `ready` a connection is established to the Redis server and the server reports 
-that it is ready to receive commands.  Commands issued before the `ready` event are queued, 
+`client` will emit `ready` a connection is established to the Redis server and the server reports
+that it is ready to receive commands.  Commands issued before the `ready` event are queued,
 then replayed just before this event is emitted.
 
 ### "connect"
@@ -129,11 +141,11 @@ you are free to try to send commands.
 
 `client` will emit `error` when encountering an error connecting to the Redis server.
 
-Note that "error" is a special event type in node.  If there are no listeners for an 
-"error" event, node will exit.  This is usually what you want, but it can lead to some 
+Note that "error" is a special event type in node.  If there are no listeners for an
+"error" event, node will exit.  This is usually what you want, but it can lead to some
 cryptic error messages like this:
 
-    mjr:~/work/node_redis (master)$ node example.js 
+    mjr:~/work/node_redis (master)$ node example.js
 
     node.js:50
         throw e;
@@ -156,7 +168,7 @@ It would be nice to distinguish these two cases.
 
 `client` will emit `drain` when the TCP connection to the Redis server has been buffering, but is now
 writable.  This event can be used to stream commands in to Redis and adapt to backpressure.  Right now,
-you need to check `client.command_queue.length` to decide when to reduce your send rate.  Then you can 
+you need to check `client.command_queue.length` to decide when to reduce your send rate.  Then you can
 resume sending when you get `drain`.
 
 ### "idle"
@@ -171,8 +183,43 @@ port and host are probably fine.  `options` in an object with the following poss
 
 * `parser`: which Redis protocol reply parser to use.  Defaults to `hiredis` if that module is installed.
 This may also be set to `javascript`.
-* `return_buffers`: defaults to false.  If set to `true`, then bulk data replies will be returned as node Buffer 
+* `return_buffers`: defaults to `false`.  If set to `true`, then all replies will be sent to callbacks as node Buffer
 objects instead of JavaScript Strings.
+* `detect_buffers`: default to `false`. If set to `true`, then replies will be sent to callbacks as node Buffer objects
+if any of the input arguments to the original command were Buffer objects.
+This option lets you switch between Buffers and Strings on a per-command basis, whereas `return_buffers` applies to
+every command on a client.
+* `socket_nodelay`: defaults to `true`. Whether to call setNoDelay() on the TCP stream, which disables the
+Nagle algorithm on the underlying socket.  Setting this option to `false` can result in additional throughput at the
+cost of more latency.  Most applications will want this set to `true`.
+* `no_ready_check`: defaults to `false`. When a connection is established to the Redis server, the server might still
+be loading the database from disk.  While loading, the server not respond to any commands.  To work around this,
+`node_redis` has a "ready check" which sends the `INFO` command to the server.  The response from the `INFO` command
+indicates whether the server is ready for more commands.  When ready, `node_redis` emits a `ready` event.
+Setting `no_ready_check` to `true` will inhibit this check.
+* `enable_offline_queue`: defaults to `true`. By default, if there is no active
+connection to the redis server, commands are added to a queue and are executed
+once the connection has been established. Setting `enable_offline_queue` to
+`false` will disable this feature and the callback will be execute immediately
+with an error, or an error will be thrown if no callback is specified.
+
+```js
+    var redis = require("redis"),
+        client = redis.createClient(null, null, {detect_buffers: true});
+
+    client.set("foo_rand000000000000", "OK");
+
+    // This will return a JavaScript String
+    client.get("foo_rand000000000000", function (err, reply) {
+        console.log(reply.toString()); // Will print `OK`
+    });
+
+    // This will return a Buffer since original key is specified as a Buffer
+    client.get(new Buffer("foo_rand000000000000"), function (err, reply) {
+        console.log(reply.toString()); // Will print `<Buffer 4f 4b>`
+    });
+    client.end();
+```
 
 `createClient()` returns a `RedisClient` object that is named `client` in all of the examples here.
 
@@ -183,15 +230,19 @@ first command after connecting.  This can be tricky to coordinate with reconnect
 etc.  To make this easier, `client.auth()` stashes `password` and will send it after each connection,
 including reconnections.  `callback` is invoked only once, after the response to the very first
 `AUTH` command sent.
+NOTE: Your call to `client.auth()` should not be inside the ready handler. If
+you are doing this wrong, `client` will emit an error that looks
+something like this `Error: Ready check failed: ERR operation not permitted`.
 
 ## client.end()
 
 Forcibly close the connection to the Redis server.  Note that this does not wait until all replies have been parsed.
 If you want to exit cleanly, call `client.quit()` to send the `QUIT` command after you have handled all replies.
 
-This example closes the connection to the Redis server before the replies have been read.  You probably don't 
+This example closes the connection to the Redis server before the replies have been read.  You probably don't
 want to do this:
 
+```js
     var redis = require("redis"),
         client = redis.createClient();
 
@@ -200,17 +251,19 @@ want to do this:
         console.log(reply.toString());
     });
     client.end();
+```
 
-`client.end()` is useful for timeout cases where something is stuck or taking too long and you want 
+`client.end()` is useful for timeout cases where something is stuck or taking too long and you want
 to start over.
 
 ## Friendlier hash commands
 
-Most Redis commands take a single String or an Array of Strings as arguments, and replies are sent back as a single String or an Array of Strings.  When dealing with hash values, there are a couple of useful exceptions to this.
+Most Redis commands take a single String or an Array of Strings as arguments, and replies are sent back as a single String or an Array of Strings.
+When dealing with hash values, there are a couple of useful exceptions to this.
 
 ### client.hgetall(hash)
 
-The reply from an HGETALL command will be converted into a JavaScript Object by `node_redis`.  That way you can interact 
+The reply from an HGETALL command will be converted into a JavaScript Object by `node_redis`.  That way you can interact
 with the responses using JavaScript syntax.
 
 Example:
@@ -229,7 +282,7 @@ Output:
 Multiple values in a hash can be set by supplying an object:
 
     client.HMSET(key2, {
-        "0123456789": "abcdefghij",
+        "0123456789": "abcdefghij", // NOTE: the key and value must both be strings
         "some manner of key": "a type of value"
     });
 
@@ -245,9 +298,10 @@ Multiple values may also be set by supplying a list:
 ## Publish / Subscribe
 
 Here is a simple example of the API for publish / subscribe.  This program opens two
-client connections, subscribes to a channel on one of them, and publishes to that 
+client connections, subscribes to a channel on one of them, and publishes to that
 channel on the other:
 
+```js
     var redis = require("redis"),
         client1 = redis.createClient(), client2 = redis.createClient(),
         msg_count = 0;
@@ -270,9 +324,10 @@ channel on the other:
 
     client1.incr("did a thing");
     client1.subscribe("a nice channel");
+```
 
 When a client issues a `SUBSCRIBE` or `PSUBSCRIBE`, that connection is put into "pub/sub" mode.
-At that point, only commands that modify the subscription set are valid.  When the subscription 
+At that point, only commands that modify the subscription set are valid.  When the subscription
 set is empty, the connection is put back into regular mode.
 
 If you need to send regular commands to Redis while in pub/sub mode, just open another connection.
@@ -294,23 +349,23 @@ name as `channel`, and the message Buffer as `message`.
 
 ### "subscribe" (channel, count)
 
-Client will emit `subscribe` in response to a `SUBSCRIBE` command.  Listeners are passed the 
+Client will emit `subscribe` in response to a `SUBSCRIBE` command.  Listeners are passed the
 channel name as `channel` and the new count of subscriptions for this client as `count`.
 
-### "psubscribe" (pattern, count) 
+### "psubscribe" (pattern, count)
 
 Client will emit `psubscribe` in response to a `PSUBSCRIBE` command.  Listeners are passed the
 original pattern as `pattern`, and the new count of subscriptions for this client as `count`.
 
 ### "unsubscribe" (channel, count)
 
-Client will emit `unsubscribe` in response to a `UNSUBSCRIBE` command.  Listeners are passed the 
+Client will emit `unsubscribe` in response to a `UNSUBSCRIBE` command.  Listeners are passed the
 channel name as `channel` and the new count of subscriptions for this client as `count`.  When
 `count` is 0, this client has left pub/sub mode and no more pub/sub events will be emitted.
 
 ### "punsubscribe" (pattern, count)
 
-Client will emit `punsubscribe` in response to a `PUNSUBSCRIBE` command.  Listeners are passed the 
+Client will emit `punsubscribe` in response to a `PUNSUBSCRIBE` command.  Listeners are passed the
 channel name as `channel` and the new count of subscriptions for this client as `count`.  When
 `count` is 0, this client has left pub/sub mode and no more pub/sub events will be emitted.
 
@@ -319,6 +374,7 @@ channel name as `channel` and the new count of subscriptions for this client as
 `MULTI` commands are queued up until an `EXEC` is issued, and then all commands are run atomically by
 Redis.  The interface in `node_redis` is to return an individual `Multi` object by calling `client.multi()`.
 
+```js
     var redis  = require("./index"),
         client = redis.createClient(), set_size = 20;
 
@@ -335,6 +391,8 @@ Redis.  The interface in `node_redis` is to return an individual `Multi` object
         .scard("bigset")
         .smembers("bigset")
         .keys("*", function (err, replies) {
+            // NOTE: code in this callback is NOT atomic
+            // this only happens after the the .exec call finishes.
             client.mget(replies, redis.print);
         })
         .dbsize()
@@ -344,6 +402,7 @@ Redis.  The interface in `node_redis` is to return an individual `Multi` object
                 console.log("Reply " + index + ": " + reply.toString());
             });
         });
+```
 
 `client.multi()` is a constructor that returns a `Multi` object.  `Multi` objects share all of the
 same command methods as `client` objects do.  Commands are queued up inside the `Multi` object
@@ -352,10 +411,11 @@ until `Multi.exec()` is invoked.
 You can either chain together `MULTI` commands as in the above example, or you can queue individual
 commands while still sending regular client command as in this example:
 
+```js
     var redis  = require("redis"),
         client = redis.createClient(), multi;
 
-    // start a separate multi command queue 
+    // start a separate multi command queue
     multi = client.multi();
     multi.incr("incr thing", redis.print);
     multi.incr("incr other thing", redis.print);
@@ -373,10 +433,12 @@ commands while still sending regular client command as in this example:
         console.log(replies); // 102, 3
         client.quit();
     });
+```
 
-In addition to adding commands to the `MULTI` queue individually, you can also pass an array 
+In addition to adding commands to the `MULTI` queue individually, you can also pass an array
 of commands and arguments to the constructor:
 
+```js
     var redis  = require("redis"),
         client = redis.createClient(), multi;
 
@@ -387,6 +449,7 @@ of commands and arguments to the constructor:
     ]).exec(function (err, replies) {
         console.log(replies);
     });
+```
 
 
 ## Monitor mode
@@ -395,11 +458,12 @@ Redis supports the `MONITOR` command, which lets you see all commands received b
 across all client connections, including from other client libraries and other computers.
 
 After you send the `MONITOR` command, no other commands are valid on that connection.  `node_redis`
-will emit a `monitor` event for every new monitor message that comes across.  The callback for the 
+will emit a `monitor` event for every new monitor message that comes across.  The callback for the
 `monitor` event takes a timestamp from the Redis server and an array of command arguments.
 
 Here is a simple example:
 
+```js
     var client  = require("redis").createClient(),
         util = require("util");
 
@@ -410,7 +474,7 @@ Here is a simple example:
     client.on("monitor", function (time, args) {
         console.log(time + ": " + util.inspect(args));
     });
-
+```
 
 # Extras
 
@@ -418,7 +482,7 @@ Some other things you might like to know about.
 
 ## client.server_info
 
-After the ready probe completes, the results from the INFO command are saved in the `client.server_info` 
+After the ready probe completes, the results from the INFO command are saved in the `client.server_info`
 object.
 
 The `versions` key contains an array of the elements of the version string for easy comparison.
@@ -432,6 +496,7 @@ The `versions` key contains an array of the elements of the version string for e
 
 A handy callback function for displaying return values when testing.  Example:
 
+```js
     var redis = require("redis"),
         client = redis.createClient();
 
@@ -439,6 +504,7 @@ A handy callback function for displaying return values when testing.  Example:
         client.set("foo_rand000000000000", "some fantastic value", redis.print);
         client.get("foo_rand000000000000", redis.print);
     });
+```
 
 This will print:
 
@@ -451,6 +517,7 @@ Note that this program will not exit cleanly because the client is still connect
 
 Boolean to enable debug mode and protocol tracing.
 
+```js
     var redis = require("redis"),
         client = redis.createClient();
 
@@ -459,10 +526,11 @@ Boolean to enable debug mode and protocol tracing.
     client.on("connect", function () {
         client.set("foo_rand000000000000", "some fantastic value");
     });
+```
 
 This will display:
 
-    mjr:~/work/node_redis (master)$ node ~/example.js 
+    mjr:~/work/node_redis (master)$ node ~/example.js
     send command: *3
     $3
     SET
@@ -477,12 +545,11 @@ This will display:
 
 ## client.send_command(command_name, args, callback)
 
-Used internally to send commands to Redis.  For convenience, nearly all commands that are published on the Redis 
+Used internally to send commands to Redis.  For convenience, nearly all commands that are published on the Redis
 Wiki have been added to the `client` object.  However, if I missed any, or if new commands are introduced before
 this library is updated, you can use `send_command()` to send arbitrary commands to Redis.
 
-All commands are sent as multi-bulk commands.  `args` can either be an Array of arguments, or individual arguments,
-or omitted completely.
+All commands are sent as multi-bulk commands.  `args` can either be an Array of arguments, or omitted.
 
 ## client.connected
 
@@ -490,7 +557,7 @@ Boolean tracking the state of the connection to the Redis server.
 
 ## client.command_queue.length
 
-The number of commands that have been sent to the Redis server but not yet replied to.  You can use this to 
+The number of commands that have been sent to the Redis server but not yet replied to.  You can use this to
 enforce some kind of maximum queue depth for commands while connected.
 
 Don't mess with `client.command_queue` though unless you really know what you are doing.
@@ -509,10 +576,38 @@ Current delay in milliseconds before a connection retry will be attempted.  This
 Multiplier for future retry timeouts.  This should be larger than 1 to add more time between retries.
 Defaults to 1.7.  The default initial connection retry is 250, so the second retry will be 425, followed by 723.5, etc.
 
+### Commands with Optional and Keyword arguments
+
+This applies to anything that uses an optional `[WITHSCORES]` or `[LIMIT offset count]` in the [redis.io/commands](http://redis.io/commands) documentation.
+
+Example:
+```js
+var args = [ 'myzset', 1, 'one', 2, 'two', 3, 'three', 99, 'ninety-nine' ];
+client.zadd(args, function (err, response) {
+    if (err) throw err;
+    console.log('added '+response+' items.');
+
+    // -Infinity and +Infinity also work
+    var args1 = [ 'myzset', '+inf', '-inf' ];
+    client.zrevrangebyscore(args1, function (err, response) {
+        if (err) throw err;
+        console.log('example1', response);
+        // write your code here
+    });
+
+    var max = 3, min = 1, offset = 1, count = 2;
+    var args2 = [ 'myzset', max, min, 'WITHSCORES', 'LIMIT', offset, count ];
+    client.zrevrangebyscore(args2, function (err, response) {
+        if (err) throw err;
+        console.log('example2', response);
+        // write your code here
+    });
+});
+```
 
 ## TODO
 
-Better tests for monitor mode, auth, disconnect/reconnect, and all combinations thereof.
+Better tests for auth, disconnect/reconnect, and all combinations thereof.
 
 Stream large set/get values into and out of Redis.  Otherwise the entire value must be in node's memory.
 
@@ -520,22 +615,51 @@ Performance can be better for very large values.
 
 I think there are more performance improvements left in there for smaller values, especially for large lists of small values.
 
-## Contributors
+## How to Contribute
+- open a pull request and then wait for feedback (if
+  [DTrejo](http://github.com/dtrejo) does not get back to you within 2 days,
+  comment again with indignation!)
 
+## Contributors
 Some people have have added features and fixed bugs in `node_redis` other than me.
 
-In order of first contribution, they are:
-
-*  [Tim Smart](https://github.com/Tim-Smart)
-*  [TJ Holowaychuk](https://github.com/visionmedia)
-*  [Rick Olson](https://github.com/technoweenie)
-*  [Orion Henry](https://github.com/orionz)
-*  [Hank Sims](https://github.com/hanksims)
-*  [Aivo Paas](https://github.com/aivopaas)
-*  [Paul Carey](https://github.com/paulcarey)
-*  [Pieter Noordhuis](https://github.com/pietern)
-*  [Vladimir Dronnikov](https://github.com/dvv)
-*  [Dave Hoover](https://github.com/redsquirrel)
+Ordered by date of first contribution.
+[Auto-generated](http://github.com/dtrejo/node-authors) on Wed Jul 25 2012 19:14:59 GMT-0700 (PDT).
+
+- [Matt Ranney aka `mranney`](https://github.com/mranney)
+- [Tim-Smart aka `tim-smart`](https://github.com/tim-smart)
+- [Tj Holowaychuk aka `visionmedia`](https://github.com/visionmedia)
+- [rick aka `technoweenie`](https://github.com/technoweenie)
+- [Orion Henry aka `orionz`](https://github.com/orionz)
+- [Aivo Paas aka `aivopaas`](https://github.com/aivopaas)
+- [Hank Sims aka `hanksims`](https://github.com/hanksims)
+- [Paul Carey aka `paulcarey`](https://github.com/paulcarey)
+- [Pieter Noordhuis aka `pietern`](https://github.com/pietern)
+- [nithesh aka `nithesh`](https://github.com/nithesh)
+- [Andy Ray aka `andy2ray`](https://github.com/andy2ray)
+- [unknown aka `unknowdna`](https://github.com/unknowdna)
+- [Dave Hoover aka `redsquirrel`](https://github.com/redsquirrel)
+- [Vladimir Dronnikov aka `dvv`](https://github.com/dvv)
+- [Umair Siddique aka `umairsiddique`](https://github.com/umairsiddique)
+- [Louis-Philippe Perron aka `lp`](https://github.com/lp)
+- [Mark Dawson aka `markdaws`](https://github.com/markdaws)
+- [Ian Babrou aka `bobrik`](https://github.com/bobrik)
+- [Felix Geisendörfer aka `felixge`](https://github.com/felixge)
+- [Jean-Hugues Pinson aka `undefined`](https://github.com/undefined)
+- [Maksim Lin aka `maks`](https://github.com/maks)
+- [Owen Smith aka `orls`](https://github.com/orls)
+- [Zachary Scott aka `zzak`](https://github.com/zzak)
+- [TEHEK Firefox aka `TEHEK`](https://github.com/TEHEK)
+- [Isaac Z. Schlueter aka `isaacs`](https://github.com/isaacs)
+- [David Trejo aka `DTrejo`](https://github.com/DTrejo)
+- [Brian Noguchi aka `bnoguchi`](https://github.com/bnoguchi)
+- [Philip Tellis aka `bluesmoon`](https://github.com/bluesmoon)
+- [Marcus Westin aka `marcuswestin2`](https://github.com/marcuswestin2)
+- [Jed Schmidt aka `jed`](https://github.com/jed)
+- [Dave Peticolas aka `jdavisp3`](https://github.com/jdavisp3)
+- [Trae Robrock aka `trobrock`](https://github.com/trobrock)
+- [Shankar Karuppiah aka `shankar0306`](https://github.com/shankar0306)
+- [Ignacio Burgueño aka `ignacio`](https://github.com/ignacio)
 
 Thanks.
 

package/benches/hiredis_parser.js

@@ -0,0 +1,38 @@
+var Parser = require('../lib/parser/hiredis').Parser;
+var assert = require('assert');
+
+/*
+This test makes sure that exceptions thrown inside of "reply" event handlers
+are not trapped and mistakenly emitted as parse errors.
+*/
+(function testExecuteDoesNotCatchReplyCallbackExceptions() {
+  var parser = new Parser();
+  var replies = [{}];
+
+  parser.reader = {
+    feed: function() {},
+    get: function() {
+      return replies.shift();
+    }
+  };
+
+  var emittedError = false;
+  var caughtException = false;
+
+  parser
+    .on('error', function() {
+      emittedError = true;
+    })
+    .on('reply', function() {
+      throw new Error('bad');
+    });
+
+  try {
+    parser.execute();
+  } catch (err) {
+    caughtException = true;
+  }
+
+  assert.equal(caughtException, true);
+  assert.equal(emittedError, false);
+})();

package/benches/re_sub_test.js

@@ -0,0 +1,14 @@
+var client = require('../index').createClient()
+  , client2 = require('../index').createClient()
+  , assert = require('assert');
+
+client.once('subscribe', function (channel, count) {
+  client.unsubscribe('x');
+  client.subscribe('x', function () {
+    client.quit();
+    client2.quit();
+  });
+  client2.publish('x', 'hi');
+});
+
+client.subscribe('x');

package/{tests → benches}/reconnect_test.js

@@ -1,4 +1,6 @@
-var redis = require("redis").createClient();
+var redis = require("../index").createClient(null, null, {
+//    max_attempts: 4
+});
 
 redis.on("error", function (err) {
     console.log("Redis says: " + err);
@@ -24,4 +26,4 @@ setInterval(function () {
             console.log(now + " Redis reply: " + res);
         }
     });
-}, 200);
+}, 100);

package/changelog.md

@@ -1,6 +1,41 @@
 Changelog
 =========
 
+## v0.7.2 - April 29, 2012
+
+Many contributed fixes. Thank you, contributors.
+
+* [GH-190] - pub/sub mode fix (Brian Noguchi)
+* [GH-165] - parser selection fix (TEHEK)
+* numerous documentation and examples updates
+* auth errors emit Errors instead of Strings (David Trejo)
+
+## v0.7.1 - November 15, 2011
+
+Fix regression in reconnect logic.
+
+Very much need automated tests for reconnection and queue logic.
+
+## v0.7.0 - November 14, 2011
+
+Many contributed fixes. Thanks everybody.
+
+* [GH-127] - properly re-initialize parser on reconnect
+* [GH-136] - handle passing undefined as callback (Ian Babrou)
+* [GH-139] - properly handle exceptions thrown in pub/sub event handlers (Felix Geisendörfer)
+* [GH-141] - detect closing state on stream error (Felix Geisendörfer)
+* [GH-142] - re-select database on reconnection (Jean-Hugues Pinson)
+* [GH-146] - add sort example (Maksim Lin)
+
+Some more goodies:
+
+* Fix bugs with node 0.6
+* Performance improvements
+* New version of `multi_bench.js` that tests more realistic scenarios
+* [GH-140] - support optional callback for subscribe commands
+* Properly flush and error out command queue when connection fails
+* Initial work on reconnection thresholds
+
 ## v0.6.7 - July 30, 2011
 
 (accidentally skipped v0.6.6)