But there is thread switching going on all the time. The more threads,
the more switching overhead.
I don't think we talk about the same threads.
python is an interpreted language. There is absolutely no overhead in
switching a python context. Nothing similar with a regular os thread switch.
python generators iteration are an example of python contexts use at no
cost.
well, in my understanding the proposal was to mix the conventional
threaded execution of 'regular' requests (which allows you to run each
request straight through, without async-specific contortions) with
async handling of ajax requests. One thread cannot at the same time
run a single request straight through and at the same time hop around
between additional async'ed ones. So, you would have to dedicate one
or more threads exclusively to the async'ed handling of ajax requests.
I'm really sorry bothering you with so many questions.
I thought that the 'Async' word in AJAX, was the about the way the
request is made at the client side.
If I understand correctly, async means that the script does not block
when waiting for the server response.
At the server side, I see no difference how this request is handled,
compared to any http request.
In simple ajax examples on the web, the script calls a really simple php
script like any other, except that it responds javascript instead of html...
If someone could explain, I would be grateful...
Thanks
-------------------------------------------------------
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
