У Няд, 09/11/2008 у 15:21 -0800, Geoff B піша:
> On Nov 9, 4:08 pm, Geoff B <[EMAIL PROTECTED]> wrote:
> With cache_classes = false (i.e., development), we get "a monkey" the
> first time we hit the page, and "not a monkey" on subsequent requests.
> This occurs whether or not we apply Tom Lea's patch.
We can ease the pain of running such code in development by not
reloading all classes after each request. But reloading only changed
classes or reloading all classes if something has changed. There were a
plugin which tried to reload only changed clasess. It didn't work for
us. So I created (and haven't published yet) a simpler solution which
reloads everything only if anything has changed. We can put this code
into rails.

Also we can ease development pain for such cases by restaring whole
process instead of reloading classes. CGI should work fine here for
example. Doing it other way seems non-trivial, because new process will
need to inherit connected socked from old process but nothing else.

-- 
Aliaksey Kandratsenka <[EMAIL PROTECTED]>


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to