On Apr 15, 2010, at 2:37 PM, Grary wrote: > > Hi, > > Is there a compelling reason to prefer reliance on the params hash vs. > the same info stored in a session hash? So, for example, params[:id] = > @loan vs. session[:loan_id] = @loan.id? It matters because I can make > prettier urls if I store certain uniquely identifying model attributes > as session variables. > > The drawback I can think of in preferring session variables to the > params hash is that a user cannot be guaranteed to recover via the > same url the same model instance under the session-preferred approach, > because the session variable may have changed. > > Thanks for any comment, > > Grar
Server farms are one reason, but with cookie-based session store, it's not that big a deal. The other reason that comes to mind is Web crawling. Relying on session state often defeats Web crawlers, although that does not seem like it's relevant to the example you gave. Why can't you make load_id part of the URL using routing? -- 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.
