On Jan 12, 9:12 am, Francisco javier Baena <[email protected]> wrote: > > The book I am following, explains together the ActiveRecord store for > sessions and the RESTful authentication, so I'm afraid I have mixed up > some concepts. > > My doubt is: When using ActiveRecord storage for sessions, is this just > like using the cookie option, but with Rails automatically storing it in > the database? I mean, woul I still use it just like session[:user_id] = > @user.id and would Rails take care of storing it into the database?
Whichever the session store (cookie store, activerecord store memcache store etc.) the api (ie. how you use it in your app) is the same. > > If so, declaring sessions as a Resource, would be independent from using > ActiveRecord store, wouldn't it? > Correct. Fred > I understand that, without declaring Sessions as a resource, I wouldn't > have RESTful authentication, but the book uses ActiveRecord store, and > next, declares Sessions as a resource, and I don't know if those are > independent. > > Hope I have explained myself :) > > Thanks for your responses! > > -- > Posted viahttp://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.
