Sorry sent last email too early! BTW, just adding mutexes in patch by patch isn't really going work. > There is already a mutex that wraps the dispatch by mongrel and > another that AP wraps the dispatch w/. (We need to drop the one in the > mongrel handler). I suggest working on this stuff in a different > branch (aka my thread_safe branch :) until we've got it done. >
I'm totally cool with working on stuff in your branch. I think the bigger problem is getting your app to be threadsafe. We > should look into adding some helpful development features to find non > threadsafe code. I added a feature to my branch that warns you if you > try to modify class variables through a caccessor if it is not safe. I > made a "Thread.current.safe?" that checks if you are 1) In a thread > and 2) not inside a mutex. (all highly experimental!) I think having stuff which helps developers write thread-safe code is great although I would disagree it is a "bigger" problem. There is absolutely no point for a rails developer to write thread safe code at this point since rails itself isn't thread safe. But hopefully that won't be the case soon! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
