« Changelog History


Websocket-Rails v0.4.0 Release Notes

  • 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.