| Revision as of 17:56, 13 June 2006 edit72.245.138.82 (talk) →External links← Previous edit | Revision as of 17:57, 13 June 2006 edit undo72.245.138.82 (talk) →External linksNext edit → | ||
| Line 39: | Line 39: | ||
| * | * | ||
| Ŷ | Ŷ | ||
| <b>Test</b> | |||
Revision as of 17:57, 13 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.
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
- DWR - dinamic web remoting
- echo2
- google widget toolkit
.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
Ŷ