Options for connecting to a persistence provider
Configure and use Mongo's connection pool
Factory for getting MessageStores based on configuration
The persistence database schema as a configurable option
All Aquarium events have a client defined unique id
Renames to more meaningfull names
Implementation of the EventStore interface in the Mongo driver
Some more service orientation to master conf
Add RESTRole (and, hence, RESTActor) to known roles/actors for provisioning.
Properly (?) quote field name in JSON response for /ping.
At least, this is what is needed for the default bahavior of Lift's jsonparser.
View revisions
Also available in: Atom