In that case, I'm really puzzled. Will look into it further. Thank you.
On Wednesday, August 6, 2014 2:42:37 PM UTC-5, Anthony wrote:
>
> If you are storing sessions in files and not doing
> session.forget(response) anywhere in your code, then there should not be
> any race conditions, as the se
If you are storing sessions in files and not doing session.forget(response)
anywhere in your code, then there should not be any race conditions, as the
session files are locked in that case, which serializes all requests
(including ajax requests).
Anthony
On Wednesday, August 6, 2014 9:30:30 P
I've been looking into it, and it appears that there is a race condition
situation going on, in which it takes a little while for the session value
to be updated, and some other functionality is accessing that value before
the update is performed. I caught it by accident while debugging using
j
>
> Presumably the DOM element you are checking for the session value is not
> something that is being updated by your Ajax call.
>
Sounds plausible - I'll explore this possibility further. Thank you.
On Wednesday, August 6, 2014 12:48:48 PM UTC-5, Anthony wrote:
>
> The session is handled the
The session is handled the same with ajax requests as with any other
requests. Hard to say what's going on in this case without seeing any code.
Presumably the DOM element you are checking for the session value is not
something that is being updated by your Ajax call.
Anthony
On Wednesday, Aug
5 matches
Mail list logo
