A new understanding of wicket

Wicket translated from TSS at the end of last year: Do we need different performance layer frameworks? Today, it has aroused everyone's resonance. At the beginning, I translated this article with a casual attitude. Don't let me know. There are too many performance-layer frameworks that make people unable to determine which framework is better.

Through today's communication, I found that TSS is correct. Wicket combines all the advantages of tapestry and echo! Wicket can shield the differences between the C/S and B/S architectures. Wicket simulates the C/S structure, that is, the interaction between the client and the server is not considered. For example, when writing complex page logic using JavaScript and XMLHTTP, the client (browser) is always considered in the mind, and the request is submitted to the server, thinking: "This is two completely different environments." You need to do a lot of extra work like avoiding page refreshing. However, when wicket is used, it can be thought that it is using swing for development or VB. In this way, the so-called client (browser) and server concepts will not exist in my mind. Therefore, the client data and the server data can be separated (in fact, wicket has helped you do a lot of work, that's it ).

Even more exciting is that wicket supports different clients, such as HTML, Flash/flex, and swing. That is to say, what should I do if I suddenly change the UI Layer of the system to flex one day? According to the existing methods, I think it is very tricky (at least not very easy). In wicket, all this can be achieved through simple configuration. Do you think it is wonderful?

Alex chew pointed out that when selecting a framework, consider the following:
1. support different clients, such as HTML, Flash/flex, and swing.
2. Support the software process and reasonably separate work.
3. It is easy to maintain and can be performed in a certain way, such as MDA. Code Generate.

Wicket can meet the preceding conditions. Now, let's talk about it.
Finally, thank Alex Chew !!!

(Please note! This document shall indicate the original author Rosen Jiang and its source:Http://blog.csdn.net/rosen)