Sadeesh Viswanthan wrote: > Hi, > Rather than accessing a base methods directly, you can access some > class methods like 'process_cgi' to solve you pbm better I think. Try > http://api.rubyonrails.org/classes/ActionController/Base.html#M000523 > this one and post here whether it helps you or not. I am also > interested in knowing this. > > Thanks, > Sadeesh > > On Dec 15, 4:41�pm, Jeff Vogt <[email protected]>
Thanks for the reply. I played around with process_cgi and determined it wouldn't work for this application. Further, I went into the code for action_controller to see how session data is saved. I went as far as writing my own method that repeats the exact way session data is saved in Action Controller, but no dice. What I think is happening, is when a request is made by the client, it grabs the current session data for a given session_id, THEN executes application code (including updating in memory any changes to the session data, THEN updates the database. When we force changes to the session (by selecting sessions.data by session_id, modifying, and saving) INSIDE of a request routine, the data changes just fine, but is overwritten at the end of the request. I think. If anybody has an idea to access whatever is the temporary store for the session when it gets changed during a request, I'd love to figure this out. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
