undo initial RedisShardingClient. more advanced but still incomplete version is on the sharding-client branch. explanation in readme.

Author: Ben Buckman

README.md

@@ -71,4 +71,7 @@ Now use `sentinelClient` as a regular client: `set`, `get`, `hmset`, etc.
 
 # `RedisShardingClient`
 
-To be continued...
+**We decided to abandon this after starting to build it.** The concept was another abstraction layer that behaved transparently like a `RedisClient`, but handled sharding (on key) in the background between a ring of multiple clients.
+For our particular application (or any particular application), however, the complexity such an abstraction layer involves is not worth the trouble, and a much simpler application-specific abstraction makes a lot more sense.
+
+If anyone is interested in continuing this line of development, see the [sharding-client](https://github.com/DocuSignDev/node_redis/tree/sharding-client) branch.

index.js

@@ -1113,12 +1113,6 @@ var Sentinel = require('./lib/sentinel');
 exports.RedisSentinelClient = Sentinel.RedisSentinelClient;
 
 
-// sharding client. instantiate separately.
-var Sharding = require('./lib/sharding');
-exports.RedisShardingClient = Sharding.RedisShardingClient;
-
-
-
 exports.createClient = function (port_arg, host_arg, options) {
     var redis_client;
     var net_client;