Obviously, AJAX came.    I do not agree with "AJAX seven sins," because really like "Lively netizens" AJAX seven sins ": Yujiazhizui hang without speech," said, few inside seven sins is not created out of nothing, of Much Ado About Nothing. 

  AJAX, I said it.    In 2001, when the company continue to use the argument in the end to the two-tier structure or web application, I highlighted inspiration, said an application to the development of fat from the thin client and the client to thin client, it is the law.    This means that, I mean that the views of applications will be developed to the fat client.    I finally until this day, AJAX, you only slowly踱small sheep finally over! 

  We look at the history of the development of it.    Too old we have not said that the market was spurned by the C / S What is wrong with the two-tier structure?    !    Calculating speed, safe and mature development tools support the development of high efficiency.    Later, it felt more development, C / S two-tier structure open enough, deployment difficulties, business logic and interface logic mixed. 

  Later, we developed a distributed application.    Distributed applications using fat client (window), the middle layer components used Affairs server, a back-end database.    Feel good, the first time a so-called "framework".    Separate from the business logic and interface logic can be very good with strong functional components to provide a two-tier method of calculation incomparable superiority.    However Distributed development of distributed development difficulties.    In its first technical barriers, distributed technology not that simple, large team development demands a high level.    And Distributed Application Services server component needs the support of the majority of servers charges, which prevented the development of the market. 

  Web application?    From the beginning of the web application point of view, its focus on the fat client applications and distributed applications drawbacks: slow speed, insecurity, business logic and interface logic still a lot of mixed areas.    Most of the early web applications have failed.    Since the framework and modalities of learning, we have begun to develop applications MVC model.    Web application was accepted.    Now most of the web applications are relatively thin client.    That is only a small client dynamic code (JavaScript).    Furthermore, a model, we found that business logic and Display interface separately, and can also use components, greatly enhancing the power of this framework, some of his inferior gradually cover.    Rather, the framework ah, ah mode of the industry has become very respected, greatly promoted the development of the industry. 

  However, I feel that there are now several major risk factors: 

  1, excessive reliance on XML.    Whether talking about what you can hear XML.    XML is not that bad, but in today's increasingly complex structure, under an application of XML will be more and more vendors nor has the same standards.    On the one hand, the impact of web application portability, and will also increase the complexity of the development.    XML documents between the matter is worth studying. 

  2, excessive use of framework.    Now the application of the J2EE side, the majority use Struts framework, Struts framework, further distillation, by adding Hibernate and others.    Really need so how?    There are so many applications really so complicated?    Some properties from the point of view of the problem?    I had a colleague said, these structures added to the software really flexible, really?    I am afraid that many of them only when the code is modified code to find convenient!    Truly flexible application often write their own framework, rather than in fetters like Hibernate can not function as the framework of full support!    Now is still a client with a AJAX, very interesting. 

  There are points that do not want to say more, the work faster. 

  My view is that the low level of applications now, there are so many people truly want to a lot of messy things added, which happens to prove that the application of confusion.    AJAX the emergence of a more disrupted this situation.    Wise certainly do not care, and good things will have a good arena (Oracle, SAP ...).    In the present circumstances, it seems difficult for these JavaScript responsibility; AJAX engine based on the HTTP Request on some key issues still not fully resolved their tables.    Return to the fat client whether to market acceptance?    Mature application would require a long time, need someone from the overall situation, uniform standards, the development of standards.