The next revolution in Web Development

The next revolution in Web development: Based onRich Client + Service"Enterprise application development technology" andDynamic Web PageThe "dynamic website development technology" is completely broken (just like the C/S structure and the terminal/host structure in that year), the enterprise application development technology will enter the fourth generation, web Application Development enters the second generation. In this revolution, Ajax and WebService (referred to as concepts, not standards) are only two triggers, and the real great changes are still coming.

There are two signs of the success of this revolution:

First, Special"Business Server"Or the current application server is transformed into a "Service Server ". Why? Because the current application server serves to "generate dynamic web pages" and is behind the web server in architecture, it is used to process the so-called "dynamic content" that cannot be processed by the Web server ", as a Web server, all HTTP specifications should be considered, such as various HTTP request methods, various HTTP header labels, various body data formats, and HTTP cache logic, encoding specifications, etc. If the backend server only needs to provide "service" in the future, the spec with at least 80% HTTP protocol may not be considered or implemented (such as the request method, I think only post is enough). In this way, the architecture of the backend server can be simplified, and the operation efficiency will be improved. In addition, backend servers can also be used to enhance "service", such as session tracking, user access monitoring, and permission management.ProgramThe functions implemented by itself can be fully implemented in the "Business Server. The re-design result of this server architecture is: the current "Web container" and "Business (EJB) container" of the application server ", it is likely to be integrated into a single "Business container" in the "Business Server ". This is also one of the reasons why 7wxaop needs to embed the jetty server as a component into the framework. I think only the "server" architecture can be changed, in this revolution.

SecondCoarse-grained interface components(Such as Treeview, listview, and eidtablegrid) has become the standard support for browsers. Nowadays, DHTML/DOM is very mature. the user interface of applications based on html/DHTML/DOM/CSS can be more beautiful than any other types of application interfaces and is rich in interaction functions, in the past, there was never any interface technology that could provide developers with such fine-grained control. However, the problem occurs precisely in this fine-grained interface construction method, which leads to a serious interface production efficiency problem. At present, most of the Ajax frameworks are doing this kind of work: Building coarse-grained interface components based on this fine-grained technology, such as Dorado in China, so is 7wx in 7wxaop; another kind of work is to design brand new coarse-grained interface components, such as Adobe's flex; there is also a kind of work that has been done very early and is probably forgotten by most people, is to directly use ActiveX interface components in IE. In my opinion, no matter which coarse-grained interface component is implemented, it is best to make standard, General, and persistent interface components jointly by browser manufacturers. When Microsoft launched. net, I thought it was the ideal interface layer technology.CodeIt turned out to be "Server dynamic pages", and Sun's JSF also learned this. A project team in our company is now using SAP's webdypro, so I have a bit of doubt: the reason why industry leaders are reluctant to work on client components and do not want to change the current web application architecture is not because they do not see technical requirements, but because, their fundamental benefit lies in the lucrative variety of server-side products. The reason why Web development is so complicated may be that there may be a big conspiracy; or, with one eye closed, these industry leaders watched the vast majority of Web developers get tired, and watched independent web developers and integrators go down one by one, but I turned around and sneaked a lot of money ---- pulling far :). I am free to post this question. After six years of working as an independent IBM developer, I feel this way.

It is recommended that all web developers pay attention to the progress in these two directions and be forward-looking in technology. Otherwise, it is meaningless to keep running behind others' ass.