switched to local api for development
added first rough implementation of socket.io

First problem is that the callbacks are stacking.  Need to add them to
the collection’s prototype so they only exist once and only get called
once.
deleted unnecessary content
added sample code to backbone.sync socketio implementation

The main problem with this implementation is that backbone.sync uses a
success callback in the options param to trigger the standard parsing
behavior, removing a successfully deleted model from a collection, etc.
 This callback then needs to get called in the socket.on(“…”, foo)
callback.  But socket.on can only be executed once, otherwise the
callbacks start stacking because they get registered every time.  This
is challenging.  A much easier and less over-ridingly invasive approach
is to hook into the repository, and send realtime events out each time
something of importance changes.  Let backbone use the ajax structure
that works so well against the standard API, and simply send out
messages when new models are created.
removed references to backbone.io and switched to new method of real-time communication

See notes from previous commit.
added pending tests for realtime behavior
removed backbone.sync socket concept implementation

Going with the simpler approach
Pulled socket.io implementation out into it's own class that observes repository events
updated socketio implementation to use a channel to namespace todos
moved all references to the api url to a globals file to only need to change it in one location
added url option to change server location
downloaded socket.io.js file so it could be minified and added to requirejs without changing path in main config
Merge pull request #1 from jchansen/socket-io-integration

Socket io integration