Moving ahead for finalizing working Session Handlers#15
Conversation
updated websocket specs and refactored code
|
|
||
| module Reel | ||
| module Session | ||
| extend Celluloid |
There was a problem hiding this comment.
o_O does that... work? @digitalextremist
|
|
||
| # initializing session | ||
| def initialize_session | ||
| @bag = Store.new self |
There was a problem hiding this comment.
with the include Celluloid in store.rb below, this will cause a new actor/thread per request
|
if i understand correctly, what you are trying to do here is have timers that "expire" the data from the hash store. you're trying to use the unfortunately, as noted above, this makes each instance of the Store class an actor with its own thread. that's way too heavy per request. one solution might be to create a single instance of a StoreExpiry class (that includes Celluloid) and register expiration there... but why use another thread, when there's perfectly good reactor sitting around in the form of the reel server? see the PR i just opened to get access to the server from inside requests. celluloid#228 |
|
Yes that would be heavy creating thread per request. Will be calling |
Improving/adding test (need updation wrt Session configuration logic)
Small tweaks/ Corrected and improved Specs
Improved/new configuration,crypto,specs
Updated/improved deleting_timer,configuration,crypto and specs
overriding server constructor to get session config value during intialization
Added few basic Session examples and removed Crypto code (performance issue)
|
Merging 😃 |
Includes all recent changes i.e. -
Deleting Timersusing Celluloid#Timers=> which deletes value from outer hash automatically after expiryConfigurationlogic and its usageParserto solve failingpipelined requesttest inconnection_specKindly Review 😃 /cc: @kenichi @digitalextremist