umpf.... I can't understand why this is not working "ok". The problem lies indeed in the fact that one ajax request overwrites the session, if the session file is not there yet..... I can only guess that the logic is failing to acquire a lock before creating the (new) file .... If a request has completed yet, hence the session file is present, all goes perfectly ok (it's probably the reason why nobody else ever noticed "the glitch", and why prepending a "session.hello = 'world'" to the index function makes all go smoothly, it actually creates the session file before the two ajax requests come in) can anyone testing this confirm this behaviour? steps to reproduce: - delete session file in the session/ dir - open the index page - session file ends up with one or another formname keys, never both - reload the page - session file holds both formnames - put session.hello = 'world' in the index() function before the return dict() - delete the session file in the sessions/ dir - reload the page - session file holds both formnames
If this is indeed the behaviour, we narrowed it down to a "glitch" that happens in one case only: 2 concurrent requests comes in and there is no session file yet. We can start from there to coordinate efforts for the patch..... it's definitely not an issue with javascript. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
