Lille
2010-Jul-07 15:15 UTC
what is a session stored via the active_record_store option unique to?
Hi, After a bunch of snooping in AWDWR and Railsguides I can''t reach a good understanding to the following question: What is a session stored via the active_record_store option unique to? In other words, how does rails bind the user to their session under the active_record_store option? This concern has arisen in the following way... ...I have two use levels in my app: 1) authenticated (authlogic) and 2) unauthenticated. In case 2, I''d been persisting user data with a session variable. I''d like to treat the session in case 2 as unique to the user, but I can''t test this assumption while working on one development machine. Do I need to use some specially-prepared session variable to ensure each unauthenticated user has only their unique session under active_record_store? Thanks, Lille -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Frederick Cheung
2010-Jul-08 07:13 UTC
Re: what is a session stored via the active_record_store option unique to?
On Jul 7, 4:15 pm, Lille <lille.pengu...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi, > > After a bunch of snooping in AWDWR and Railsguides I can''t reach a > good understanding to the following question: What is a session stored > via the active_record_store option unique to? In other words, how does > rails bind the user to their session under the active_record_store > option? >The user has a cookie (by default called session_id or _session_id or something along those lines) storing the session id. Fred> This concern has arisen in the following way... > > ...I have two use levels in my app: 1) authenticated (authlogic) and > 2) unauthenticated. In case 2, I''d been persisting user data with a > session variable. I''d like to treat the session in case 2 as unique to > the user, but I can''t test this assumption while working on one > development machine. Do I need to use some specially-prepared session > variable to ensure each unauthenticated user has only their unique > session under active_record_store? > > Thanks, > > Lille-- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Maybe Matching Threads
- Rails and Service Oriented Architecture (SOA): any downsides?
- how to 'delete' an object from an association collection in-memory only
- Switching to active_record_store session management errors out
- session active_record_store
- config.action_controller.session_store = :active_record_store