On Jun 16, 10:05 am, cipher_neo <[email protected]> wrote: > I am looking for a way to synchronize access to a shared data > structure in a standard rails app. > > I read that if you are running on passenger, then Mutex.new is of no > use? Can somebody please clarify this? > > I know that I can use transaction and :lock => true to do db level > locking on models, but I have a global hash defined in an initializer > as such > > GLOBAL_DATA = Hash.new > > and I am storing data in it that will be accessed by multiple > clients... > > I would simply like to wrap access to this structure in some kind of > synchronization. > > Anyone got any suggestions?
Um, how's "don't do this" work for you? Seriously - this is an amazingly bad idea, especially once you consider scaling past one application server. Is there a reason this data couldn't just be stashed in the DB somehow? --Matt Jones -- 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.
