On Jun 8, 2012, at 5:56 PM, Jonathan Vanasco wrote:
> I think you're dealing with either a locking issue or a bug in beaker. > > check out the comments here: > https://bitbucket.org/bbangert/beaker/issue/101/naive-dog-pile-effect-implementation. > if there's a race issue with locks: """I think you misunderstand the > action of the dogpile lock. The next client which arrives, sees that > the lock is acquired, then returns the previous value. There is no > waiting of any kind.""" the dogpile lock is not used with Beaker's session implementation, so this issue is not relevant to anything to do with Pyramid's "request.session". that said, there's a crap-ton of bugs reported with Beaker's server side session implementation and I don't think anyone is fixing them. I don't recommend it, and I'd stick with client side sessions that store just some identification tokens. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
