Nathan Beyer wrote: > I think I've figured out the issue. The problem seems to be that in > development, the class caching was disabled by default, so the classes > were reloaded on every request, but the initializers aren't re-run, > which is can be rather painful.
Yes, I would expect that class caching is disabled in development. It would certainly be painful if it wasn't disabled. As I understand it the disabling of the caching is done to support rapid turnaround. See a problem, fix the code, refresh the page and see the fix. This should not normally be a problem as long as you don't rely on global state, which I think is good practice anyway. -- 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 -~----------~----~----~----~------~----~------~--~---
