Changelog History
Page 2
-
v0.4.4 Changes
April 28 2013
- โ Remove existing subscribers from a channel when making it private to eliminate the potential for malicious users to eavesdrop on private channels. Addresses issue #72.
- Prevent the server from crashing when receiving an uploaded file. โ Addresses issue #68.
- ๐ Allow custom routes for the WebSocket server. Users of are
no longer forced to use the
/websocket
route. - Thanks to @Cominch
-
v0.4.3 Changes
March 12 2013
- ๐ Change the log output in Channel#trigger_event. Fixes issue #61.
- Cancel the ping timer when removing disconnecting a Connection.
- ๐ Fix uninitialized constant WebsocketRails::Internal controller error.
-
v0.4.2 Changes
March 1 2013
- Check to make sure ActiveRecord is defined before calling ๐ ActiveRecord::RecordInvalid in Dispatcher. Fixes issue #54. - Thanks to @nessche
-
v0.4.1 Changes
February 28 2013
๐ Fix bug in ControllerFactory#reload! that prevented the handling of ๐ internal events when running in the Development environment. Fixes issue #50. - Thanks to @nessche
๐ Only reload controller classes when Rails config.cache_classes is set ๐ to false instead of always reloading when in the Rails development ๐ง environment. This better respects the Rails configuration options. โ Addresses issue #51. - Thanks to @ngauthier
โก๏ธ Update the Rails engine to handle the new Rails 4 route path. Checks ๐ the Rails version and adds the correct path for the routes file. Fixes issue #49. - Thanks to @sgerrand
-
v0.4.0 Changes
February 27 2013
There have been a few breaking changes in the public API since the ๐ last release. Please review the list below and consult the Wiki for more information regarding the usage of the new features.
Controller instances no longer persist between events that are triggered. Each event is processed by a new controller instance, ๐ similar to a standard Rails request. Since you can no longer use instance variables to temporarily persist data between events, there is a new Controller Data Store that can be used for this purpose. This ๐ change addresses issue #31.
๐ The original DataStore class has been deprecated. In it's place are the new Controller Data Store and Connection Data Store. As mentioned above, the Controller Data Store can be used to persist data between events in much the same way that you would use instance variables. The ๐ Connection Data Store acts like the Rails session store. Use it to store data private to a connection. Data in the Connection Data Store can be accessed from any controller. Check out the Wiki for more information on both.
๐ The
websocket_rails.reload_controllers
event has been deprecated. The new Controller instantiation model allows for automatic controller class reloading while in the development environment. You no longer need to trigger an event to pick up code changes in controllers while connections are active.Real logging support has finally been implemented. Check out the configuration WIki for more information on the various logging options available.
-
v0.3.0 Changes
February 6 2013
Extend the event router DSL to accept routes similar to the routes.rb shorthand
controller#action
. - Thanks to @nessche.โ Add a custom RSpec matcher suite for verifying event routes and easily asserting that WebsocketRails controller actions are triggering events correctly. - Also thanks to @nessche.
๐ Fix fiber yielded across threads bug when running in standalone mode by disabling Thin threaded mode as default option.
-
v0.2.1 Changes
January 29 2013
๐ Fix default redis driver issue that was causing problems when using redis while event machine was not running.
๐ Fix undefined data store value issue. Thanks to @burninggramma.
-
v0.2.0 Changes
November 25 2012
- โ Add standalone server mode to support non event machine ๐ based web servers.
-
v0.1.9 Changes
November 19 2012
๐ Fix bug that crashed the server when receiving badly formed messages through an open websocket. Fixes issue #27.
โ Add support for communication between multiple server instances and background jobs. Solves scaling problems discussed in issue #21.
๐ Fixed client_disconnected event firing twice - Thanks to @nickdesaulniers
-
v0.1.8 Changes
July 18 2012
- ๐ Fix bug in Channel#trigger preventing the data from coming through properly.