> I'd recommend not using Thread.exclusive at all it will end up > limiting rails options on alternate ruby impls. We should either wrap > a mutex around any calls to the Dependencies, or even better in > production mode we should preload all classes before any hits to the > application which would avoid this issue entirely.
Yeah, we don't even have Thread.exclusive in 1.9, so that's out. Unfortunately mutexes can't save us either, so preloading is the obvious choice. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
