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.""" or this could just be from a bug that was resolved. BUT i think this is probably a locking issue. have you looked into how pyramid_beaker frees up the locks ? it looks to me like you have the session tied up for the duration of get_slow_results , so get_progress never sees the new values. -- 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.
