The rise of Ajax, the traditional web framework dances with Wolves

The development framework of Java EE is a blossoming, from JSF, tapestry to struts, webwork, and from spring Webflow to jsp/jstl/velocity, and so on. And almost every day a new framework is born. But will the rise of Ajax or other AJAX-like client technologies mean that the traditional web-based framework for html/http will be bleak?

One, the traditional web encounter Ajax, is fusion or extinction

The traditional web framework is mainly responsible for processing HTTP requests and generating HTML pages, in the server to ensure the normal client display, mainly through the processing of forms, binding business data objects, etc. and return to the client's HTML page.

And Ajax, through the use of modular engine, XPATH/XSLT engine, SOAP protocol and Xfroms technology to achieve, fully in the client play an irreplaceable role. As a result, developers can isolate JavaScript from HTML pages as much as possible, using CSS to minimize the use of JavaScript scripting languages in the client. This is based on the JavaScript version of the Ruby on Rails framework, which can be run on the browser in a stable application.

Will future Web apps be based on static HTML and Web services that use AJAX for XML? If so, do we also need a traditional web framework based on http/html? Or completely AJAX to replace the web framework for viewing, editing and other functions?

As far as the author's personal experience is concerned, if not for free, Ajax will be a new addition to the web framework charge. But the authors are skeptical that Ajax will replace the Web framework's conclusions. Too many companies are reluctant to develop a JavaScript-only UI (user interface), and Google is no exception, because Gmail has a non-JavaScript version that works when the browser's JavaScript feature is disabled.

However, with Ajax, does the problem of using the web framework still exist? At the same time, which Ajax framework is best for you? DWR, scriptaculous, Prototype or Ajaxtags, Ajaxanywhere, Rico? More or dojo, Json-rpc? But when one of their frames is acquired by Apache, does that mean it will become another struts?

This means that the author is more inclined to integrate Ajax with the traditional web framework seamlessly. Ajax's strengths and strengths lie in its good performance in client "View", as well as requests for business data on demand from client requests. Web frameworks are weak in this area, but in other ways, such as servers, are strengths. In oversize projects, Ajax would be powerless if the architecture of the program was not built using the MVC principles of the web framework.