现在使用 GWT 2，与 wicket 等相比有什么优势? [英] Now with GWT 2, what are the advantages over wicket and likewise?

问题描述

除了 Wicket 的简单性(即 Wicket 是一个更简单的系统恕我直言)和 GWT 在客户端的响应能力(GWT 的客户端状态和 JavaScript - 可能复杂的客户端代码)以及 GWT 更大的扩展潜力的论点之外，还有什么是使用 GWT 而不是 Wicket 的论据?

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?

就我个人而言，我已经做了很多 Wicket 开发，但很久以前只是快速浏览了一下 GWT.

Personally I've done a lot of Wicket development, but have only had a quick look at GWT a long time ago.

推荐答案

基本上，GWT 是一个构建基于 javascript 的客户端的工具，因此，它最适合您想要一个基于 javascript 的客户端.

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 以服务器为中心，虽然它可以很容易地将 javascript 嵌入到无状态页面中，但服务器端状态处理是更自然的方法.

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.

使用 GWT，您的架构将变成客户端-服务器，即浏览器上的胖客户端，向服务器调用过程"(服务)，发送和接收数据.

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.

使用 Wicket(以及其他以服务器端为中心的组件框架，如 JSF 和 Tapestry)，该架构是一个更传统"的 3 层架构，发送和接收的是页面或页面的片段，而不是纯数据.

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屋！