Enhaced/fixed js library. Now on_close and on_error events pass the event straight. Tests added and fixed for this too
Merge pull request #100 from imton/master

on_close and on_error events fixed
Update jasmine gem to fix Travis build.
Fix Logging spec by stubbing Time.now with a real Time object.
Remove ruby 1.9.2 from travis.yml since Rails 4 requires > 1.9.3
Don't call unloadable on inherited controllers if Rails.version =~ 4

Fixes #101 RuntimeError (Circular dependency detected while autoloading
constant EventsController)
Add #close! method to WebSocket and HTTP connection adapters.

This provides an easy way to close a connection from within a
WebsocketRails Controller by calling connection.close!. This works
with both WebSocket connections as well as streaming HTTP connections.

This closes #99 and closes #15 as well.

As far as #15 is concerned, the pull request submitted by @imton
takes care of managing disconnects on the client side cleanly.
Granted, you still need to manually resubscribe to any events
after you reconnect. The next step will be to manage reconnects
better internally within the JavaScript client.
Bump version and update CHANGELOG for release.
Properly handle connection state and add .connection_stale function

The `on_close` and `on_error` events now properly set the connection
state to 'disconnected'.

I also added a .connection_stale() function for easily checking whether
or not the connection is active.
Update version and CHANGELOG for release.
Mention which IRC network #websocket-rails is in.
Use window.location.protocol to choose between ws:// and wss:// shcheme.
Don't break old behaviour
Output a warning to console when using urls whit protocol scheme
redundant regexp, really need to polish my regexp skills...
Merge pull request #109 from depili/master

Use window.location.protocol to choose between ws:// and wss:// shcheme.
Remove clutter from  by adding ConnectionManager#inspect
Merge branch 'master' of github.com:DanKnox/websocket-rails
Add UserMnaager for sending to specific users from anywhere in your app.

The user manager is accessible through the WebsocketRails.user method.
The key for the hash is defined in `config.user_identifier` and will
be called on the `current_user` object if one exists at the time the
connection is established. It defaults to connection.id if there is
no `current_user` object accessible or the `current_user` object does
not respond to the identifier.
Add config.user_identifier to the events.rb generator template.