When a connection is established, the connection will publish a message through Wisper
Remote connections will decode their message and then publish the message through wisper
Fixing typo in travis file
We now have a rake task to run the Angler server, and the Angler server itself can now be executed through said rake task to listen for connections. use 'rake angler:run'.
We now have the callback for connection establishment on post_init, as connection_completed does not seem to fire at all.
we don't support ruby 1.9.2
Rakefile adjusted so Travis has it's own rake task. I don't like the solution but Travis doesnt' seem to like installing gems properly (i.e, EventMachine)
OK this is getting annoying now, perhaps I should learn how gemspecs work
please work, travis-ci senpai
I am going to rage if Travis does not work now
.___. TRAVIS-CI PLS
A start on the message decoder requirements
Altering README for installation instructions
Merge branch 'status-screen' of github.com:DanPantry/angler
My word, that was a lot of work, but now the server can respond to ClientChangeState messages!
A little moving things about and forcing the Remote to have a :Handshaking state when it is initially connected
Why is gemfile.lock here..
Do not add gemfile.lock to our commits
We now respond to ClientStatusRequest
We now respond to client status ping