The short and sweet: you can not, should not, and will not try to save information in memory in your Rails environment across web requests. If you need to save data, use a database, use the session, use flat files on the disk. Expecting Ruby to "just remember" is pointless here because 1) yes, development environment reloads everything on each request and 2) production deploy environments run mutiple instances of Rails processes so you're never guarenteed to get the same process for subsequent requests.
Jason On Fri, Jan 30, 2009 at 2:43 PM, Ball Balla <[email protected]> wrote: > > Does it make sense to make a singleton class in Rails? I made a > singelton class but everytime I do model.instance.id in some controller > it is always different. Is this because it is in development mode so the > classes get reloaded each time but in production this would not be the > case? > -- > Posted via http://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 -~----------~----~----~----~------~----~------~--~---
