Clean AJAX
From Wikipedia, the free encyclopedia
| Clean AJAX | |
| Developer: | Carlos Eduardo Gonçalves |
|---|---|
| Latest release: | 4.1.0 / November 4, 2006 |
| Use: | Ajax framework |
| License: | GPL |
| Website: | clean-ajax.sourceforge.net |
Clean AJAX is an open source, cross browser AJAX engine, inspired on Java Message Service, that uses messages to control the requests. It is an easy to use solution that provides message queue, garbage collection, XSLT support, encryption, web service access, history and cache.
Contents |
[edit] Design
Clean AJAX was designed to represent AJAX requests as messages, which offers a well established model to deal with asynchronous communication. Messages offer a very flexible model, where we are able to combine plain attributes to get many different behaviours at request and/or response.
It can be plugged in any page or DHTML framework because it was designed in comformation with the separation of concerns principle, keeping focus on AJAX issues.
[edit] Structure
Clean AJAX can be deployed using different configurations (all and tiny). A configuration allows that architects and developers, can determine the amount of resources consumed by the engine at runtime.
Clean AJAX includes two open source projects as libraries. Google AJAXSLT project was added to Clean to grant XSLT support on browsers that don't have native support for it. Paul Johnstone JavaScript implementations for MD5 and SHA1 algorithms, were added to Clean to provide secure AJAX requests.
[edit] Features
- A high level of abstraction, you can use just one facade to work with AJAX.
- Configuration by exception, the messages require mimimum explicit configuration to work.
- Simple way to customize message's behaviour and apply your own logic to them.
- Multiple request handle, the engine is able to handle multiple requests simultaneously.
- Exception handle, the engine is aware about exceptions that can occur and how to report them.
- Trace console to monitor messages life cycle.
- Cache and history control.
- Message queue used to manage the requests.
- Garbage collection.
- Integration with web services based on SOAP and XMLRPC protocols.
- Cross-browser implementation compatible with the major browsers.
