moved database connection code into it's own module
added socket.io
initial implementation of socket.io when bus was also acting as CRUD interface
removed db access code from socket.io implementation

It was placed there when I was experimenting with using it as the CRUD
interface, but that was too messy with Backbone.  Much simper solution
was to only use it to broadcast changes.  The client is responsible for
broadcasting changes if they want other people see them.  TODO:
consider shifting the updates into the CRUD API.  PROBLEM: We don’t
want to broadcast the change to client responsible for the event, but
don’t know who they are during the CRUD call.  To get around that we’d
have to have the client check (for create) if a model already existed
(meaning they were the one who instigated the message).  But that might
not work because it’s possible the CREATE message would return before
the AJAX response, and then the AJAX response might cause the same
model to be added twice.