I have my thread safe branch setup already. I'm just toying around w/ some ideas right now. I'll actually start working on it when this Google Code thing kicks off.
http://github.com/josh/rails/commits/thread_safe On Apr 11, 10:55 pm, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: > > I'd really like Rails to be thread safe and I totally think it's a > > doable feat. I'd like to help out as much as I can so if anyone knows > > of any problem areas please point me towards them. > > I think it's an achievable feat too, but I'm a little hesitant to > just whack mutexes everywhere we find a race condition. Instead I'd > like to think a little more about the changes which are needed to make > the thing work and rejig the internals to make the task simpler. > > I'd suggest a candidate first-task is tidying up the ActiveRecord > allow_concurrency stuff to use a connection pool rather than blindly > establishing a connection per thread. This would require some pretty > heavy-duty refactorings in connection_specification, but it should be > reasonably straightforward. If anyone's interested in starting with > this, I'd be happy to collaborate and host a thread-safety branch on > my github account as a staging area before we include it for 'whatever > comes after 2.1'. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
