We've all seen the amazing results you can get when you start using
Ajax, they all come down to one thing: speed.
Question is, how is such a speed-up accomplished? The standard answer
is that a complete trip to the server is averted, but this is not true,
in fact a complete cycle does occur:
1) Request to server
2) Possible db access on server
3) rendering of HTML on server
4) delivery to browser
5) re-rendering of portions of screen
Supposedly the js and css libraries are cached so we have not saved the
effort of retrieving them, this means the only thing we have saved is
the effort of re-rendering the screen from scratch. To put another way,
we have not saved a whole lot of bytes of traffic, or CPU cycles on the
server. The only thing that seems to be missing is the
render-from-scratch on the browser.
Is this correct? And if so, why is it so dramatically expensive to
render a page from scratch, that Ajax could make such a dramatic
improvement to the situation?
begin:vcard
fn:Kenneth Downs
n:Downs;Kenneth
adr;dom:;;347 Main Street;East Setauket;NY;11733
email;internet:[EMAIL PROTECTED]
tel;work:631-689-7200
tel;fax:631-689-0527
tel;cell:631-379-0010
x-mozilla-html:FALSE
url:http://www.secdat.com
version:2.1
end:vcard
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
