Head First Ajax | Search for a title, author or keyword | |||||||||||||||
Head First Ajax by Rebecca M. Riordan, 2008. With traditional web pages and applications, every time a user clicks on something, the browser sends a request to the server, and the server responds with a whole new page. Even if your user’s web browser is smart about caching things like images and cascading style sheets, that’s a lot of traffic going back and forth between their browser and your server... and a lot of time that the user sits around waiting for full page refreshes. Using Ajax, your pages and applications only ask the server for what they really need—just the parts of a page that need to change, and just the parts that the server has to provide. That means less traffic, smaller updates, and less time sitting around waiting for page refreshes. And best of all, an Ajax page is built using standard Internet technologies, things you probably already know how to use, like: XHTML, CSS and Javascript.
|
| |||||||||||||||
Head First Ajax | Disclaimer: this link points to content provided by other sites. |