Ajax superior to the reasons for the JSF

Abstract: Ajax superior to the reasons for the JSF

</ Td> </ tr> <tr> <td height="35" valign="top" class="ArticleTeitle"> <table width = "100%" border = "0" cellspacing = "0" cellpadding = " 0 "> <tr> <td height="65" align="left" valign="top"> </ td> </ tr> </ table>

Articles for reference purposes only. Author unknown.
Why produce a Sun JSF, JSF Why is like this now, I think the reasons for this: First, component-based Web development will be a future trend. Since the IDE contains components to facilitate the handling, and improve development efficiency.

That is to say, better than Struts JSF / MVC framework WebWork such advantages is that it can integrate with the IDE to automatically generate code. The traditional manual prepared by the pure MVC framework, the impact of development efficiency. Because of Java technology on the client side and there was no obvious advantage. Applet swap has been abandoned, the strengths of Java on the server side. Sun can not go to the use of JavaScript, because in the eyes of traditional developers, JS only qualified to be one very trivial task.

So in the design of this system, all users are on the incident to deal with the server-side, this decision caused JSF fatal shortcomings. It dealt with the case in the server model tied down, limits the response of the more sensitive interactive design. The attendant network delay the availability of the software would be destroyed. This is Ajax in the framework of the JSF could not give full play to the role of reasons.

JSF imitate the design of a VB, components of the development of this direction is correct, Ajax development and will take this path. However, JSF and VB VB is the biggest difference between the models are in local events to deal with. This is an intrinsically different, so if JSF does want to imitate VB, which are also Dongshixiaopin. JSF and in the design phase, synchronous request / response in the mainstream, their ideas are still firmly based on the pages bound in the development of means. There is no other thought possible.

Asynchronous request / response is Ajax with the traditional development mode biggest difference, asynchronous bring a better interactive design.

Ajax in Action in Chapter 1 of the author cites a compelling example. When users of Google Maps rolling map, a map of access to the new picture, since it is asynchronous request, it will not interrupt the user's operational procedures. In the traditional map services, each may need to refresh rolling pages. Microsoft used to map services that can be clearly felt the gap, it does not allow users or simply rolling on the map.

Http://terraserver.microsoft.com/

I said before Google Maps is not Ajax, because there is no use of XMLHttpRequest, some say this understanding seems narrow. Google Maps request map picture, of the dynamic created by the amendment of the img src attribute of the element, such a request would not interrupt the user's operation, it is asynchronous. We see Ajax in Action authors Google Maps as Ajax applications, and the author of Pragmatic Ajax said Google Maps is not the strict sense of Ajax, the two statements are justified.

In fact, if the JSF and Applet combination may be better. Applet is a multi-thread, the user can capture operation, using asynchronous send to the server. This will not interrupt the operation of the user. But such a design of this structure to the complex. Applet and has already decided to discard things. JSF and Java Web Start can be combined, but JWS designed to build a completely different type of Web application that Rich Client, and not designed to run on the browser built within the RIA applications. So JSF is only a maximum transition programme, in the Ajax / Flash competition is not already scenery.

Future browser-based RIA development, Ajax, Flash are two of the most promising technologies.

Zexin accordance with the judgement may be a world, Ajax, Flash / Flex / Laszlo, and the M $ Atlas. Atlas is similar to M $ Flash development of a technology, also is a vaporware, did not see its true colors. Java Web Start contrast limited to internal applications.

In the future the performance of the client may not develop Java position, which is reluctant to see the Sun, but Sun in this competition is only a small role.