On Sun, Dec 13, 2009 at 4:40 PM, Yehuda Katz <wyc...@gmail.com> wrote: > Long-term, we want to try to get away from using global state like > this as much as possible, but fixing it can sometimes open a thorny > can of worms. Koz's solution, paired with a mutex or thread-local (for > threadsafe scenarios) is a good workaround for now.
Any updates on this? Has any progress been made on making ActiveResource thread-safe (either in Rails 3 or in plugins/forks)? Thanks, -- Chad -- 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 rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
