Okay, continuing in my project of abusing Rails horribly. It looks to me like even standard Rails sessions are subject to a race condition if the same session is accessed concurrently. Request1 checks out a session. Request 2 checks out a session, makes a change, and writes it back to the store. Request 1, still finishing up, makes a change, and writes the session back to the store... overwriting the changes Request2 made.
So, if I'm using an ActiveRecord store... what happens if I just add a lock_version column to the model? But then I guess an exception will be raised from the innards of ActiveController somewhere. And it would be unclear how to recover from it. So that's not quite right. Has anyone come up with an optimistic locking solution for Rails session to get around this race condition issue? -- 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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
