Tuesday, June 13th, 2006p>“A” may stand for Asynchronous, but PPK recently asked his readers if people are really exploiting the asynchronous nature of Ajax. Are there really situations where the user can do something while a request takes place? For instance, GMail makes an asynchronous call to grab some mail data – do you actually play around with other controls while the data downloads? Probably not. So he’s wondering…
(W)hether asynchronous communication is all that it’s cracked up to be from a practical point of view. If in practice it’s not useful to initiate a new request while waiting for the response to a previous request, Ajax’s main user interface advantage is kind of nullified.
The comments to that post indicate there are indeed practical uses of asynchrony … he’s subsequently summarized four kinds of asynchronous usage:
- Sending data to the server (AKA fire-and-forget)
- Refreshing data (AKA polling, Periodic Refresh)
- This is the (as yet single) example of Ajax as I always supposed it would work: quietly but incessantly refreshing the page content based on repeated user actions
- New “pages” (AKA Microlink)
Posted by Michael Mahemoff at 5:38 am