StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to optimize a web based application against latency due to multiple asynchronous requests in background?
text
Body
copied!<p>I am designing a modular RIA based on thin server client side MVC architecture. Right now, The application is only complete to the extent of 10% and as such it is not too late to incorporate design changes. </p> <p>The application is designed in such way that it initially loads with a very small footprint and depending on the action performed by the user, large volumes of data are fetched asynchronously. This data potentially would include both data stored in my servers as well as data from third party web services including social networking and microblogging services.</p> <p>However what I am concerned about is that, is it possible that multiple data heavy ajax requests running in background stall the browser ? I have recently observed some serious latency problems in some social content aggregation services and upon analysing the client side code I was surprised that the application footprint of the client side was quite small, well within 300KB. However, when running the application very often the browser (both Firefox and IE) hanged and took several seconds to recover. Upon analysing the asychronous requests it appeared that the application was simultaneously fetching user content from gmail, facebook and twitter and pushing them into the DOM and was taking too much of memory resources. </p> <p>It would be great if someone could point me to some guidelines/best practices to prevent such issues. Would it be advisable to write a custom wrapper script that loads the content in background sequentially in a pre-specified order of importance rather than loading them all in parallel, which might eventually result in several callbacks getting executed in parallel. </p> <p>Any advise would be heavily appreciated. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload