现在与GWT 2相比，Wicket有什么优势？ [英] Now with GWT 2, what are the advantages over wicket and likewise?
问题描述
除了检票的简单的参数（即，检票是一个更简单的系统IMHO）和GWT的响应在客户端（GWT的客户端状态和JavaScript - 潜在的复杂的客户端代码）和GWT的用于缩放更大的潜力，是什么使用GWT超过Wicket的争论？
就我个人而言，我已经做了很多Wicket开发，但很久以前只能快速浏览GWT。
基本上，GWT是构建基于JavaScript的客户端的工具，因此，如果您想要一个基于JavaScript的客户端。
Wicket以服务器为中心，尽管它可以很容易地将javascript嵌入到无状态页面中，但服务器端状态处理自然的方法。
必须注意的是架构是非常不同的。
使用GWT，您的架构变成客户端服务器，浏览器上的胖客户端，向服务器调用'程序'（服务），发送和接收数据。
使用Wicket（以及其他服务器端为中心的组件框架，如JSF和Tapestry），该体系结构是更传统的3层结构，发送和接收的内容包括页面或碎片的页面，而不是纯数据。
虽然你当然可以混合使用适应其他架构，它根本就不会很自然。
人们倾向于关注'哪个更容易使用'（这完全是主观的，取决于您的背景）或'哪个更漂亮，哪个部件更多'，但不应低估架构差异，这会影响您必须采取的处理安全性和可伸缩性等方面的方法。
Apart from the argument of Wicket's simplicity (that is, Wicket is a simpler system IMHO) and GWT's responsiveness in the client (GWT's client side state and JavaScript - potentially complex client side code) and GWT's greater potential for scaling, what is the argument for using GWT over Wicket?
Personally I've done a lot of Wicket development, but have only had a quick look at GWT a long time ago.
The advantages are, basically, that GWT is a tool to build javascript-based client, thus, it's best suited if you want a javascript-based client.
Wicket centers on the server, and while it makes it quite easy to embed javascript into stateless pages, server-side state handling is the more natural approach.
One must note that the architectures are very different.
With GWT, your architecture turns into client-server, a thick client on the browser, making calls to 'procedures' (services) to the server, sending and receiving data.
With Wicket (and other server-side-centric component frameworks, like JSF and Tapestry), the architecture is a more 'traditional' 3-layer one, and what is sent and received are pages or fragments of the pages, not pure data.
While you can certainly blend both to adapt to the other architecture, it simply wouldn't be very natural.
People tend to focus on 'which is easier to use' (which is completely subjective, depending on your background), or 'which is more beautiful and has more components', but one should not underestimate the architectural difference, which affects the approach you have to take to handle aspects like security and scalability.
这篇关于现在与GWT 2相比，Wicket有什么优势？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
