Let me decide how to connect to redis so I can run on Heroku
A second pass at a simpler demo of the JSON API cargo culted from Hex
Standardize indent to 2 characters rather than beautify-js's standard 4.
Fix #140 by waiting to send the auth message until after the connection is fully open.
A few typo fixes to examples/index.html

Just some English grammar edits.
Remove hostname and let browser do it's job

Hard coding port to 8000 will prevent the exampleserver from running
with it's port option -p, removing it.
Fixed noop try statements in db tests
Execute safe queries by default.

The mongodb library was throwing large warnings that "The default of false will change to true in the near future" and that "This message will disappear when the default safe is set on the driver Db".
Add opsCollectionPerDoc option to Mongo storage.

If this is true, each document will have its own collection for its operations. If false, operations are put in a single large operations table keyed by docname. The former is faster and requires less storage, but does not easily scale beyond 12,000 or so documents (the maximum number of collections per database) and does not seem compatible with Mongo's sharding.
Fix detach_ace - not all listeners were being removed
Merge branch 'websocket'
Disable EventEmitter warning for number of listeners on a doc
it's reasonable to have more than 10 users working on a doc
Merge branch 'eventemitter'
Fix doc creation race condition
two doc objects could be created if two clients open the doc simultaneously
Merge branch 'doc-load-race'
Replace aws2js with awssum

awssum is a more robust and better supported library. This will allow us
to get request headers when requests fail which is important for debugging
issues with Amazon support.
Remove dynamo dependence for awssum

Remove our dependency on the node dynamo module and use the awssum module
instead as it's better supported.
Add retry behavior to all dynamo requests.

We will try every operation 5 times, with an exponentially growing
time between them. It will start at 500 milliseconds and grow by a
factor of 1.5.
Add retry behavior to all S3 requests.

We will try every operation 5 times, with an exponentially growing
time between them. It will start at 500 milliseconds and grow by a
factor of 1.5.
Allow configuration of s3, dynamo regions.

Previously the same region was used for both S3 and Dynamo, these are
now independent.