What about initializing the object with the params values? Something like
foo = MyObject.new(params[:foo]) On Aug 6, 9:27 am, Max Williams <[email protected]> wrote: > pepe wrote: > > How about saving the object in a session value? > > > session[:my_object] = my_object/@my_object > > > The next action could just retrieve it easily: > > > my_object/@my_object = session[:my_object] > > > Pepe > > This isn't what the session is for. It's bad practise imo to use the > session as a storage space for any arbitrary data - it's going to fill > up with a load of junk real quickly. What if two different actions > happen to use the same session variable name? What if you want to get > to step two of the process from somewhere else, that didn't save the > session variable? It's just asking for trouble. Keep the session data > to an absolute minimum. > > If you're doing something based on the submission of a form, then that > should depend on what the form sends through, not on the form and some > stuff that you hope is in the session. That way you can look at the > form and see what's going on, without knowing about some mysterious > session stuff. > -- > 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 -~----------~----~----~----~------~----~------~--~---
