Ajax = one page less submit

Many people on the Internet say That Ajax applicationsProgramIt should be one page one application. I think this is not suitable for my current development model.

Each application has its own special structure. I have seen a lot of applications using one page one application, such as turboajax, and so on. However, there are some problems with the popularization of such programs in China.

First, the purpose of the CMS system is to be searched and searched online. If Ajax is used, these pages do not have a fixed address and cannot be searched by search engines or by browsers. This is what many CMS operators do not want to see. Such a system is similar to the Flash RIA and has similar problems.

II. If you re-use the opoa architecture in a new system, many of the previously developedCodeThe template must be rewritten. System maintenance is inconvenient.

So I will not consider using the opoa Design Model for the moment. Instead, some functions of the system are transformed through Ajax.

The most typical form is to fill in a table. Many forms are very complex in format. Let's talk about the resume. A table is usually divided into different parts. For example, the appfuse demo. This problem can be avoided if Ajax is used. Enter it in one interface. Some data can be quietly stored in the background session first. The last one-time submit is submitted.

Of course, in this case, Ajax is a bit cool, but it is still necessary. Excessive submit, in addition to making the customer suffer a lot of speed impact on the interface. (Modern webapps have a large proportion of artists ). In addition, many status labels must be maintained on the server.

Trackback: http://tb.blog.csdn.net/TrackBack.aspx? Postid = 477490