I haven't understood why ajax requests require a busy thread to be
handled.
Is it because the tcp connection is not closed between the requests?
Why ajax requests are not handled like standard http requests, using a
session Id to maintain the per client state (with a new tcp connection
per request)?
They are handled like standard requests. The issue is that (in my older
implementation) the request would be made to the server, and the server
would sit around with that request for TIMEOUT seconds. The problem is
when you have multiple users connecting (or even several ajax-enable
pages viewed in rapid succession), many of the threads from webware's
thread pool are used for up to TIMEOUT seconds. Once the threads are all
busy, the next user trying to connect must wait until a busy thread
finishes its current task before that user's request is served.
With the changes I posted to the wiki this morning, the ajax_response
requests are not held up on the server side, so the limit of concurrent
users goes up (a lot). The problem is not really solved, per se, but
it's impact is weakened.
--John
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Webware-discuss mailing list
Webware-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/webware-discuss
