Two different methods of Ajax Development

Ajax applications in recent years Program There are two completely different methods in development. Each method extends the previous structure model. because the two methods seem to be different in nature, one of them should be selected in actual application development.

When we first hear the term Ajax, our first response may be its high web page interactivity, at least necessary for Web applications in JavaScript.CodeAlthough there are consistent opinions on the significance of Ajax applications, there are some differences between developers on how to interact with JavaScript or how to allocate the display logic between the client and the server.

In recent months, artima has reported several Java-centric fat client frameworks to completely hide developers' interaction with JavaScript. these frameworks integrate Javascript into the JSF component to process JavaScript as a tool. The details are hidden for developers. leveraging the advantages of the JSF server presentation model, Ajax-based JSF presents the component state on the client.

On the contrary, Ajax has advantages in some client component Toolkits. For example, Dojo or prototype not only presents JavaScript to users, but also makes it easier for developers to develop page-type applications. for example, the dojo toolkit provides many APIs that simulate important parts of j2se APIs, such as the Collector and validators. in addition, the UI tool, such applications will not only play a role in the display logic, but even some business logic on the client, these business logic will be encoded using JavaScript. interaction with the server is restricted in this situation, that is, the client application must interact with external resources, for example, extract data to the client or save user changes to the data.

Because the Ajax-based JSF method is executed on the presentation layer of the server and the Ajax features are integrated into the component, it looks like an extension of the thin client, in addition, it is the direct derivation of traditional Web applications. The subtle feature of this method is the Sun Ray thin client device, which displays desktop images on the server, the client can process up to one dedicated display. the second method is a client-server extension, so that the application logic is displayed between the client and the server. in Ajax, the client is a programmable web browser.

These two types of violations are based on good practices. They are different systems in application development. Thin Clients involve the incompatibility of JavaScript Execution in browsers, they seldom involve whether the thin client model is preferred, even if all browsers can display JavaScript very well.

However, JavaScript is still difficult in terms of development logic. In a new version, ecmascript 4 provides a completely object-oriented language because it is quite standard, browser execution is compatible. in addition, the client class library has concealed most of the incompatibility of browsers.

Client supporters believe that their methods can better use local computer resources, which also leads to replacement of traditional desktop applications in applications, even if there is no persistent network connection.

Experienced users think that each method has its own advantages and disadvantages. If you develop a brand new fat client application, you have to choose either a thin client or a client-server model.