Fix for [GH-165] - createClient to properly assign parser_module
Add comma to package.json
Add failing test.

The test demonstrates failure for the following scenario. A single-subscription
client calls unsubscribe immediately followed by a subscribe. It will fail when
it tries to receive the next pmessage/message because the client will be in
false pub_sub_mode. Here is why it is false: First, the 2nd subscribe sets
pub_sub_mode to true during send_command. Next, the unsubscribe's
return_reply sets pub_sub_mode to false. The 2nd subscribe's return_reply does
not re-set pub_sub_mode back to true. So the result is a client with false
pub_sub_mode that fails upon receipt of the next message or pmessage.
Add fix for last test (re-establish pub_sub_mode = true)
Try to workaround a bug in the multi/exec logic
Update index.js
remove duplicate "take either"
Merge pull request #206 from bluesmoon/patch-1

remove duplicate "take either"
Fix package.json format

Signed-off-by: David Trejo <david.daniel.trejo@gmail.com>
git ignore node_modules

Signed-off-by: David Trejo <david.daniel.trejo@gmail.com>
readme: add a few missing contributors to the list
package.json: add a few missing contributors
readme: add more contributors
index.js: fix missing .EXEC alias
Fix for [GH-165] - createClient to properly assign parser_module

Signed-off-by: David Trejo <david.daniel.trejo@gmail.com>
package.json: add dtrejo as maintainer
Removed reference to individual `args` argument

When the second argument of `send_command` is not an array, the following
error is thrown:

    Error: send_command: second argument must be an array

Signed-off-by: David Trejo <david.daniel.trejo@gmail.com>
readme: highlight js examples
readme: warn that code in callbacks to commands in a multi are not atomic
readme: info on how to select a different db