I’ve been using Synchronous XMLHTTP calls in several web applications. Some of the applications are in production and running well for a while now without any problems.
In my most recent web app:
Scenario 1:
I’m using synchronous calls ie 5 calls onLoad for each of the forms. Each of the calls returns a small snippet of xml data (less than 300 bytes) which contains the database path for a different database. This information is parsed and stored in JS variables and used on other events like input onChange etc.
Scenario 2:
I’ve also used CFD fields and dblookups to achieve the same.
On comparison I found the page loads more faster in Scenario 1 than in Scenario 2.
One more scenario where I use sync calls is to get information from a view based on a key value (dblookup simulation), where I get for eg: 10 item values (concatenated in one column) in one sync call instead of 10 async calls and then parse the return value and update the webpage without a page reload.
So far I haven’t faced any kind of problems either in production or in development environments with xmlhttp sync calls. I’m happy the way xmlhttp sync calls are working. But recently I read some articles and a lot of them suggested not to use sync calls. My only concern is about what I’ve read on the internet rather than what I’ve experienced with xmlhttp sync calls.
Can anybody throw some suggestions/improvements as to whether to use or not use synchronous xmlhttp calls. Any kind of input/criticism is most welcomed.
TIA
Sai