У Суб, 04/10/2008 у 17:35 +0200, Michael Koziarski піша: > Aliaksey Kandratsenka wrote: > > У Суб, 04/10/2008 у 15:26 +0200, Michael Koziarski піша: > > > >> These cover several different areas, and I'd prefer lighthouse tickets > >> in general. Feel free to combine all the checkout ones into one ticket. > > Ok, I'll post tickets. > >> However with: > >> > >> http://github.com/alk/rails/commit/db5d9aef00703e695335e8357608f7061fda35e9 > >> > >> Reloading isn't thread safe and *can't* be due to the way constant > >> definition works in ruby. Why are you doing it in production mode? > >> allow_concurrency should be false for development mode? Is it not? > >> > > The problem is that allow_concurrency mutex doesn't protect class > > reloading. And in development mode under webrick when 2 subsequent > > requests come from different connection we have one thread trying to > > execute some action and other thread doing #cleanup_application. > > Sure, but you've unconditionally introduced the mutex, it should only be > there for allow_concurrency = true. You mean allow_concurrency = false ?
-- 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 -~----------~----~----~----~------~----~------~--~---
