Thanks for the quick reply Niphlod. That was the first thing I tried but it 
didn't help. Am I doing forget() correctly if I read a session attribute 
and then call forget but never write to the session (until later of course)?

Something I forgot to mention, some, but not all, the controller functions 
access the DB (sqlite) but just read.

On Thursday, April 7, 2016 at 12:04:41 PM UTC-7, Niphlod wrote:
>
> IMHO it's just sessions being locked to prevent concurrent modifications. 
>
> if your ajax requests aren't using the session, put a 
>
> session.forget(response)
>
> at the top of your function.
>
> http://web2py.com/books/default/chapter/29/04/the-core#session
>
> On Thursday, April 7, 2016 at 8:46:16 PM UTC+2, MDSIII wrote:
>>
>> Running web2py from the Wing IDE, so using the built-in rocket server, I 
>> see long Waiting times in Chrome Dev Tools for my ajax requests. I'm 
>> getting times in excess of 6 or 8 seconds.
>> This is a single page application that fires off a bunch (7 or 8) ajax 
>> requests after the initial page load. I'm not sure how to confirm it but it 
>> seems as though the server is handling these requests serially.
>> When I make a request to one of these long wait controller functions 
>> singly (either non-xhr or with xhr) it returns pretty quick (< 1 sec.).
>> If I start web2py from console I don't see these long wait times.
>>
>> I'm pretty sure this is due to how wing manages worker threads but I'm 
>> hoping someone here also uses Wing for development and knows why this 
>> happens and a "fix". I don't remember it always being like this on previous 
>> versions.
>>
>> Using wing 5.1.10
>> and web2py 2.13.4
>>
>> Thanks,
>>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
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/d/optout.

Reply via email to