Frederick Cheung wrote in post #1028961: > In theory I don't think this is needed because different threads > should be using different connection objects (there's supposed to be a > pool of connection objections, and any member of the pool is only ever > used by one thread at a time. You might also want to ask on the rails- > core list
Seems practice disagrees with that theory. At least we had exceptions due to unsynchronized cache access. And we ourselves did not introduce any threads in the code. I'll see whether I get answers here. If not, I'll gladly accept your advice and take it on to rails-core. Best regards Stefan -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
