Varangian wrote:
my question is when to use Asynchronous Pages and when to not?
Considering their advantage of not locking the UI thread for a
particular process whether long or not, I might think that it is
worthwhile to
use them for every single page, whatever the process.... but I may be
wrong.
what do you think?
Thanks!
Most web pages only fetch data once, so it's more efficient to just send
a complete page instead of making several requests to first get the page
and the fill it with data.
If you change the contents of the page, you often want the URL to
reflect the change, so you simply load a new page.
It's mostly for a bit more complicated scenarios, where you don't have
pages that can be indexed by search engines anyway, that asynchronous
pages can be handy.
--
Göran Andersson
_____
http://www.guffa.com