Ajax
What the heck is AJAX? Everybody moves towards AJAX...
Ajax meant (Asynchronous JavaScript with XmlHttpRequest)
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 - retrieving data, crunching numbers, talking to various legacy systems - and then returns an HTML page to the client.
Figure 1: The traditional model for web applications (left) compared to the Ajax model (right).
This approach makes a lot of technical sense, but it doesn't make for a great user experience. While the server is doing its thing, what's the user doing? That's right, waiting. And at every step in a task, the user waits some more.
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.
Here are few Major Open source Ajax..
http://ajax.schwarz-interactive.de/csharpsample/default.aspx
http://goog-ajaxslt.sourceforge.net/
ASP.NET 2.0 comes with ClientCallBack function does the same functionality.
More info: Click here
Ajax meant (Asynchronous JavaScript with XmlHttpRequest)
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 - retrieving data, crunching numbers, talking to various legacy systems - and then returns an HTML page to the client.
Figure 1: The traditional model for web applications (left) compared to the Ajax model (right).
This approach makes a lot of technical sense, but it doesn't make for a great user experience. While the server is doing its thing, what's the user doing? That's right, waiting. And at every step in a task, the user waits some more.
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.
Here are few Major Open source Ajax..
http://ajax.schwarz-interactive.de/csharpsample/default.aspx
http://goog-ajaxslt.sourceforge.net/
ASP.NET 2.0 comes with ClientCallBack function does the same functionality.
More info: Click here
posted by Srini at
3:54 PM
0 Comments:
Post a Comment
<< Home