Ajax component frameworks.

 

Components are generally created via JavaScript or XML tags, or by adding special attributes to normal HTML elements. These frameworks are generally larger, and intended for web applications rather than web sites. However, Some component frameworks require the developer to have extensive HTML/CSS/Ajax experience and to do cross-browser testing. Users can get the benefits from the following Ajax components frameworks:
1 – Customization APIs and related technology
2 – More programmatic control and flexibility
3 – Advance skinning facilities and structure
4 – Allow users to create new components based on other components

“Indirect” Ajax Framework.

 

Indirect frameworks therefore require knowledge of the high-level language, CSS and HTML, and do not necessarily require a user to have a great deal of Ajax or advance Javascript knowledge. The Indirect frameworks are typically accompanied by convenient libraries, modules and classes.
Examples of Indirect Ajax frameworks include Google Web Toolkit, and RubyJS, here are some of the benefits of “indirect” Ajax framework: 

The build in high-level web widget sets of the Indirect Ajax frameworks have far more in common with Desktop widgets. Able to create code that takes care of browser incompatibilities at run-time. A ASP.NET AJAX developer can program the web front-end in the same programming language as that which the server-side code is written. The ASP.NET AJAX developer can have the flexibility to create their own Ajax framework using programming concepts.