Misplaced Pages

Ajax framework: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 06:25, 9 June 2006 editDavid.Mestel (talk | contribs)Rollbackers5,396 editsm Reverted edits by 221.134.7.78 (talk) to version 57540357 by 68.213.254.226 using VandalProof← Previous edit Revision as of 16:14, 9 June 2006 edit undo70.25.231.110 (talk) Why a framework?Next edit →
Line 4: Line 4:
==Why a framework?== ==Why a framework?==
In the article that has coined the "Ajax" term, J.J. Garrett describes Ajax as a layer between the user interface and the server. This Ajax engine is intended to suppress waiting for the user when the page attemps to access the server. The goal of the framework is to provide this Ajax engine, and all the required functions, server side and client side. In the article that has coined the "Ajax" term, J.J. Garrett describes Ajax as a layer between the user interface and the server. This Ajax engine is intended to suppress waiting for the user when the page attemps to access the server. The goal of the framework is to provide this Ajax engine, and all the required functions, server side and client side.

Article Link: http://www.adaptivepath.com/publications/essays/archives/000385.php


==ColdFusion frameworks== ==ColdFusion frameworks==

Revision as of 16:14, 9 June 2006

Ajax is a technology to build dynamic web pages on the client side. Data is read from the server or sent to the server by JavaScript requests.
However, some processing at the server side is required to handle requests, i.e., finding and storing the data. This is accomplished more easily with the use of a framework dedicated to process Ajax requests.

Why a framework?

In the article that has coined the "Ajax" term, J.J. Garrett describes Ajax as a layer between the user interface and the server. This Ajax engine is intended to suppress waiting for the user when the page attemps to access the server. The goal of the framework is to provide this Ajax engine, and all the required functions, server side and client side.

Article Link: http://www.adaptivepath.com/publications/essays/archives/000385.php

ColdFusion frameworks

Libraries include ajaxCFC, CFAjax, JSMX, SRS, and WddxAjax.

PHP frameworks

These may be very simple libraries such as Sajax, or more complete tools, such as Sarissa, that can interact with various databases.

Java frameworks

tanaji

.NET frameworks

Microsoft has created a framework for .NET, ATLAS, which is a set of extensions to ASP.NET. Ajax.NET is an independent framework that works under .NET and uses ASP.NET.

JavaScript extensions

On the client side, there are numerous extensions to JavaScript that provide all the functions to interact avec the XMLHttpRequest object, including extensions to the user interface. Rico is an example of open source JavaScript library for Ajax.

See also

External links