adaptive path » ajax: a new approach to web applications
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
- ajax
- , web
- , javascript
- , programming
- , xml
- , design
- , web2.0
- , development
- , xmlhttprequest
- , technology
- , webdev
- , webdesign
- , article
- , css
- , reference
- , html
Bookmark History
Saved by 328 people (-107 private), first by anonymouse user on 2006-03-02
- Donaldkal on 2009-10-15 - Tags From , Internet , Explorer , Ajax
- Davirtavares on 2009-07-13 - Tags JavaScript
- Whikloj on 2009-06-17 - Tags Web , Development , AJAX
- Tripleee on 2009-04-13 - Tags 000tbd , 20060619-0123 , javascript , xml , development , site , www
- Scop22 on 2008-10-27 - Tags imported , Bookmarks , ICT , Reference , Ajax
Public Sticky notes
Ajax: A New Approach to Web Applications
Highlighted by chanio
Asynchronous JavaScript + XML
Highlighted by michigan
How Ajax is Different
An Ajax application eliminates the start-stop-start-stop nature of interaction on the Web by introducing an intermediary — an Ajax engine — between the user and the server. It seems like adding a layer to the application would make it less responsive, but the opposite is true.
Instead of loading a webpage, at the start of the session, the browser loads an Ajax engine — written in JavaScript and usually tucked away in a hidden frame. This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. The Ajax engine allows the user’s interaction with the application to happen asynchronously — independent of communication with the server. So the user is never staring at a blank browser window and an hourglass icon, waiting around for the server to do something.
Highlighted by z_julio
n Ajax engine
Highlighted by yaateehshima
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript XML, and it represents a fundamental shift in what019s possible on the Web
Highlighted by earlybert
Defining Ajax
Ajax isn’t a technology. It’s really several technologies, each flourishing in its own right, coming together in powerful new ways
Highlighted by frankbenneker
If anything about current interaction design can be called “glamorous,” it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.
Despite this, Web interaction designers can’t help but feel a little envious of our colleagues who create desktop software. Desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences we can provide and the experiences users can get from a desktop application.
That gap is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps. Zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by cvdlinden
Google is making a huge investment in developing the Ajax approach. All of the major products Google has introduced over the last year — Orkut, Gmail, the latest beta version of Google Groups, Google Suggest, and Google Maps — are Ajax applications. (For more on the technical nuts and bolts of these Ajax implementations, check out these excellent analyses of Gmail, Google Suggest, and Google Maps.) Others are following suit: many of the features that people love in Flickr depend on Ajax, and Amazon’s A9.com search engine applies similar techniques.
These projects demonstrate that Ajax is not only technically sound, but also practical for real-world applications. This isn’t another technology that only works in a laboratory. And Ajax applications can be any size, from the very simple, single-function Google Suggest to the very complex and sophisticated Google Maps.
Highlighted by piggex
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by lbukys
Ajax
Highlighted by yellow0212
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript XML, and it represents a fundamental shift in what019s possible on the Web.
Defining Ajax
Ajax isn019t a technology. It019s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:
standards-based presentation using XHTML and CSS;
dynamic display and interaction using the Document Object Model;
data interchange and manipulation using XML and XSLT;
asynchronous data retrieval using XMLHttpRequest;
and JavaScript binding everything together.
The classic web application model works like this: Most user actions in the interface trigger an HTTP request back to a web server. The server does some processing 014 retrieving data, crunching numbers, talking to various legacy systems 014 and then returns an HTML page to the client. It019s a model adapted from the Web019s original use as a hypertext medium, but as fans of The Elements of User Experience know, what makes the Web good for hypertext doesn019t necessarily make it good for software applications.
Highlighted by rlmrdl
Defining Ajax
Ajax isn019t a technology. It019s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:
standards-based presentation using XHTML and CSS;
dynamic display and interaction using the Document Object Model;
data interchange and manipulation using XML and XSLT;
asynchronous data retrieval using XMLHttpRequest;
and JavaScript binding everything together.
Highlighted by pklausner
Ajax: a New Approach to Web Applications
Highlighted by cheekywombat
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by lbukys
Ajax: A New Approach to Web Applications
Highlighted by miyamah
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript XML, and it represents a fundamental shift in what019s possible on the Web.
Highlighted by ironick
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by jahmount
Google is making a huge investment in developing the Ajax approach. All of the major products Google has introduced over the last year — Orkut, Gmail, the latest beta version of Google Groups, Google Suggest, and Google Maps — are Ajax applications. (For more on the technical nuts and bolts of these Ajax implementations, check out these excellent analyses of Gmail, Google Suggest, and Google Maps.) Others are following suit: many of the features that people love in Flickr depend on Ajax, and Amazon’s A9.com search engine applies similar techniques.
These projects demonstrate that Ajax is not only technically sound, but also practical for real-world applications. This isn’t another technology that only works in a laboratory. And Ajax applications can be any size, from the very simple, single-function Google Suggest to the very complex and sophisticated Google Maps.
Highlighted by piggex
This engine is responsible for both rendering the interface the user sees and communicating with the server on the user’s behalf. The Ajax engine allows the user’s interaction with the application to happen asynchronously — independent of communication with the server
Highlighted by dcorking
Ajax: A New Approach to Web Applications
Publications Sections:
* Reports
* Latest essay
* Essay archives
* Newsletter
* Reading list
Recent Essays
* Ajax: A New Approach to Web Applications
February 18, 2005
* Nine Resolutions for 2005
January 6, 2005
* Making A Better CMS
November 15, 2004
* Metadata for the Masses
October 19, 2004
* User Research Abroad: Handle Logistics in Four Easy Steps
September 16, 2004
Essay Archives »
by Jesse James Garrett
February 18, 2005
If anything about current interaction design can be called “glamorous,” it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.
Despite this, Web interaction designers can’t help but feel a little envious of our colleagues who create desktop software. Desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences we can provide and the experiences users can get from a desktop application.
That gap is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps. Zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by tzon02
Ajax: A New Approach to Web Applications
Publications Sections:
* Reports
* Latest essay
* Essay archives
* Newsletter
* Reading list
Recent Essays
* Ajax: A New Approach to Web Applications
February 18, 2005
* Nine Resolutions for 2005
January 6, 2005
* Making A Better CMS
November 15, 2004
* Metadata for the Masses
October 19, 2004
* User Research Abroad: Handle Logistics in Four Easy Steps
September 16, 2004
Essay Archives »
by Jesse James Garrett
February 18, 2005
If anything about current interaction design can be called “glamorous,” it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.
Despite this, Web interaction designers can’t help but feel a little envious of our colleagues who create desktop software. Desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences we can provide and the experiences users can get from a desktop application.
That gap is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps. Zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by tzon02
Ajax: A New Approach to Web Applications
Publications Sections:
* Reports
* Latest essay
* Essay archives
* Newsletter
* Reading list
Recent Essays
* Ajax: A New Approach to Web Applications
February 18, 2005
* Nine Resolutions for 2005
January 6, 2005
* Making A Better CMS
November 15, 2004
* Metadata for the Masses
October 19, 2004
* User Research Abroad: Handle Logistics in Four Easy Steps
September 16, 2004
Essay Archives »
by Jesse James Garrett
February 18, 2005
If anything about current interaction design can be called “glamorous,” it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online.
Despite this, Web interaction designers can’t help but feel a little envious of our colleagues who create desktop software. Desktop applications have a richness and responsiveness that has seemed out of reach on the Web. The same simplicity that enabled the Web’s rapid proliferation also creates a gap between the experiences we can provide and the experiences users can get from a desktop application.
That gap is closing. Take a look at Google Suggest. Watch the way the suggested terms update as you type, almost instantly. Now look at Google Maps. Zoom in. Use your cursor to grab the map and scroll around a bit. Again, everything happens almost instantly, with no waiting for pages to reload.
Google Suggest and Google Maps are two examples of a new approach to web applications that we at Adaptive Path have been calling Ajax. The name is shorthand for Asynchronous JavaScript + XML, and it represents a fundamental shift in what’s possible on the Web.
Highlighted by tzon02
Defining Ajax
Ajax isn%u2019t a technology. It%u2019s really several technologies, each flourishing in its own right, coming together in powerful new ways. Ajax incorporates:
standards-based presentation using XHTML and CSS;
dynamic display and interaction using the Document Object Model;
data interchange and manipulation using XML and XSLT;
asynchronous data retrieval using XMLHttpRequest;
and JavaScript binding everything together.
Highlighted by arekarlsen
Public Comment
on 2006-06-07 by chanio
on 2006-07-22 by schamess
on 2006-07-26 by seh119958
on 2006-08-01 by aquilax
on 2006-08-02 by mitten
on 2006-08-03 by nvanloen
on 2006-08-08 by jasonabate
on 2006-08-23 by bluecockatoo
on 2006-10-25 by xemaps
on 2007-02-12 by z_julio