Hi, >From what I understand, the general consensus is that you shouldn't store objects in the session, because your object references may become stale.
The LoginEngine seems to use session[:user] frequently instead of using something like session[:user_id]. How should the user be identified in the session? Is LoginEngine doing it according to the current best practices? Is it doing some magic under the covers to automatically populate the session with the current user object by the time the controller method is invoked? Thanks, Brad -- Bradley Mazurek _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
