blocks|key|1691231|text|ZK专注于服务器端，因为GWT都在浏览器中，所以ZK需要更多的ajax点击服务器来获取js片段、屏幕部分等，而GWT只是在开始下载js应用程序(它将永远缓存在客户机中)以及应用程序需要从后端获得一些数据的时候点击服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691232|说到，IMHO+GWT应该表现得更好，因为您不需要在服务器(较轻的服务器)中执行任何类型的视图逻辑，而且连接中的请求也较少。|1691233|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

ZK is server side focused, since GWT is all in the browser, so ZK needs much more ajax hits to the server to get js fragments, screen portions, etc. whereas GWT just hit the server at the beginning to download the js app (which will be cached in the client for ever) and whenever the app needs some data from the backend.

Said that, IMHO GWT should perform better since you dont need any sort of view logic being executed in the server (lighter servers), and there are less requests in the wire.

blocks|key|1075692|text|GWT和ZK在架构上有很大的不同。GWT以客户为中心，因此它向服务器发送的请求较少。使用GWT，您基本上可以自己控制一切。另一方面，这意味着开发人员负责处理服务器请求和服务器与客户端之间的异步数据传输。如果您是一个经验丰富的web开发人员，那么结果可能是伟大的。如果你不是，那么它可能是相当具有挑战性和复杂的，因为有一些网络和安全问题，你需要注意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1075693|另一方面，ZK是以服务器为中心的，它为您处理这些服务器-客户机异步通信。有了ZK，开发人员可以更多地关注业务逻辑，而无需处理客户机-服务器问题。由于框架负责客户端服务器的讨论，默认情况下会有更多的请求。如果您希望最小化请求，您可能可以按照他们的开发人员指南进行一些优化。|1075694|IMO+ZK和GWT都是比较成熟的框架。您可能会考虑您的项目需求和您在Web开发方面的经验，然后选择解决方案。|1075695|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

GWT and ZK are very different architecturally. GWT is client-centric so it sends less requests to the server. With GWT you can basically control everything by yourself. This on the otherhand means, the developer is responsible for handling server requests and asynchornouse data transfer between server and client. If you are an experienced web developer then the result could be great. If you are not then it could be pretty challenging and complex as there are some network and security issues you need to take care.

On the other hand, ZK is server-centric, it handles these server-client async communication for you. With ZK developers can focus more on the business logic without taking care of client-server issues. As the framework takes care of client-server talk, there are more requests by default. If you wish to minimize the request, you can probably follow their developer's guide to do some tuning.

IMO ZK and GWT are both matured framework. You can probably think about your project requirements and your experiences in Web development then choose the solution.

blocks|key|2169127|text|GWT和ZK是不同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2169128|我做了一些ZK项目和一些GWT项目。在这两种情况下，我都没有性能问题，但我觉得当我使用GWT时，我需要编写更多的代码。|2169129|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

GWT and ZK are kind of different. 

I've done some ZK projects and also some GWT projects. I didn't have performance issues in either cases,but I feel I need to write more code when I use GWT.

blocks|key|1691393|text|前几篇文章是基本的，但zk中有一些特性，我认为必须加以讨论。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691394|记住，每个请求都是一个zk事件，因为zk是完全基于事件的.|1691395|客户端事件处理
Zk允许您实现与服务器端一样的客户端事件处理，这包括防止zk向服务器触发事件。
您可以简单地操作js中的客户端对象，就像在服务器端用Java进行操作一样。
或者做一些后处理然后..。|ordered-list-item|offset|length|1691396|使用客户端事件触发
Zk获得了有用的js方法zAu.send(zk.Event，int)，让我们将自定义或标准事件发送到服务器。|1691397|可推迟的事件侦听器
可推迟的事件在客户端排队，这样您就可以最小化请求的数量。|1691398|司徒班
Stubonly是一种只使用组件客户端的方法。但到目前为止，这只适用于zk+EE。|1691399|因此，您可以看到，如果您愿意的话，可以将请求限制在GWT的请求数量上。|1691400|如果它有意义或没有依赖于你/你的应用程序。但我认为你可以说zk比GWT更强大。|1691401|你可能对iZUML和延迟渲染也感兴趣。|1691402|entityMap|0|LINK|mutability|MUTABLE|url|http://books.zkoss.org/wiki/ZK_Client-side_Reference/General_Control/Event_Listening|1|http://books.zkoss.org/wiki/ZK%2520Client-side%2520Reference/Communication/AU%2520Requests/Client-side%2520Firing|2|http://www.zkoss.org/javadoc/latest/jsdoc/_global_/zAu.html#send%2528zk.Event,%2520int%2529|3|http://books.zkoss.org/wiki/ZK_Developer%2527s_Reference/Event_Handling/Event_Listening#Deferrable_Event_Listeners|4|http://books.zkoss.org/wiki/ZK_Developer%2527s_Reference/Performance_Tips/Specify_Stubonly_for_Client-only_Components|5|http://www.zkoss.org/license/|6|http://books.zkoss.org/wiki/ZK%2520Client-side%2520Reference/General%2520Control/iZUML|7|http://books.zkoss.org/wiki/ZK_Developer%2527s_Reference/Performance_Tips/Defer_the_Rendering_of_Client_Widgets^0|0|0|0|7|0|0|0|9|1|M|M|2|0|0|9|3|0|0|3|4|13|5|5|0|0|0|4|5|6|A|4|7|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1I|8|@]|9|@$G|1J|H|1K|1|1L]]|A|$]]|$1|I|3|J|5|F|7|1M|8|@]|9|@$G|1N|H|1O|1|1P]|$G|1Q|H|1R|1|1S]]|A|$]]|$1|K|3|L|5|F|7|1T|8|@]|9|@$G|1U|H|1V|1|1W]]|A|$]]|$1|M|3|N|5|F|7|1X|8|@]|9|@$G|1Y|H|1Z|1|20]|$G|21|H|22|1|23]]|A|$]]|$1|O|3|P|5|6|7|24|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|25|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|26|8|@]|9|@$G|27|H|28|1|29]|$G|2A|H|2B|1|2C]]|A|$]]|$1|U|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]|14|$5|X|Y|Z|A|$10|15]]|16|$5|X|Y|Z|A|$10|17]]|18|$5|X|Y|Z|A|$10|19]]|1A|$5|X|Y|Z|A|$10|1B]]|1C|$5|X|Y|Z|A|$10|1D]]|1E|$5|X|Y|Z|A|$10|1F]]]]

The previous posts are basiclly, but there are some features in zk that,I think, must be talked about. 
Remember, every request is a zk-event, cos zk is completely event-based.

<ol>
<li><a href="http://books.zkoss.org/wiki/ZK_Client-side_Reference/General_Control/Event_Listening" rel="nofollow">Client-Side Event-Handling</a> 
Zk allows you to implement client-side event-handling just as well as server-side,
which includes preventing zk from firing an event to the server. 
You can simple manipulate the client objects in js as you can do it in Java on the 
server-side or just do some post processing and and then... </li>
<li><a href="http://books.zkoss.org/wiki/ZK%20Client-side%20Reference/Communication/AU%20Requests/Client-side%20Firing" rel="nofollow">Use Client-Side Event-Firing</a> 
Zk got that usefull js method <a href="http://www.zkoss.org/javadoc/latest/jsdoc/_global_/zAu.html#send%28zk.Event,%20int%29" rel="nofollow">zAu.send(zk.Event,int)</a> that let's you send custom
or standart events to the server.</li>
<li><a href="http://books.zkoss.org/wiki/ZK_Developer%27s_Reference/Event_Handling/Event_Listening#Deferrable_Event_Listeners" rel="nofollow">Deferrable Event-Listeners</a> 
Deferrable-events are queued at client-side, so you can minimize the number of
requests.</li>
<li><a href="http://books.zkoss.org/wiki/ZK_Developer%27s_Reference/Performance_Tips/Specify_Stubonly_for_Client-only_Components" rel="nofollow">Stubonly</a> 
Stubonly is a way to make a component client-side only. But by now this is only
available for <a href="http://www.zkoss.org/license/" rel="nofollow">zk EE</a>.</li>
</ol>

So, you can see, if you like, you can limit the requests to maybe the same amount of requests of GWT. 
If it make sense or not depandce on you/your applycation. But I think you can say that zk is more powerfull than GWT. 
You maybe interested in <a href="http://books.zkoss.org/wiki/ZK%20Client-side%20Reference/General%20Control/iZUML" rel="nofollow">iZUML</a> and <a href="http://books.zkoss.org/wiki/ZK_Developer%27s_Reference/Performance_Tips/Defer_the_Rendering_of_Client_Widgets" rel="nofollow">defer rendering</a> too.

blocks|key|1691404|text|我的经验来自于两个团队的实际项目，一个使用zk框架编写，另一个使用GWT。具有来自同一数据服务层的数据的相同UI项目。zk团队在GWT团队消耗的三分之一时间内完成了该项目。这两个项目都部署在生产中。用户对这两款应用都很满意。最后，我们在生产中保留了zk版本。为什么？仅仅是因为与GWT相比，zk应用程序的维护要快得多而且简单得多！对不起GWT..。不错的技术支持一个巨人，但我们将继续与zk。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691405|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My experience from real world projects with two teams, one writing using the zk framework and the second using GWT. Identical UI projects having data served from the same data service layer. The zk team completed the project in one third of the time the GWT team consumed. Both projects deployed in production. Users were happy using either app. Finally we kept the zk version in production. Why? Simply because the maintenance of the zk app was so much faster and simple compared to GWT! Sorry GWT... Nice technology backed up by a giant but we will keep going with zk.

Hi I am trying to compare the performance of zk and gwt.

In my comparision I cant write any javascript by myself if the framework itself converts some code into js its ok(like gwt) but I cant write js by myself

On writing code in the above way for almost anything done on browser a request is sent to the server in ZK.

Hence eventually if you compare the no of request sent by zk to server is too high as compared to gwt.

i would like to ask the following.

<ol>
<li>whose performance is better zk or gwt while ignoring the above.</li>
<li>if we dont ignore the above then is my conclusion that gwts performance is better than zk right ?</li>
</ol>

I know that there might be other parameters when comparing performance... but if the difference between requests are so high i cant really see zk beating gwt which some people have said on some forums

pls help
thanks

zk vs gwt zk too many requests

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

嗨，我试着比较zk和gwt的性能。在我的比较中，如果框架本身将一些代码转换为js，它的ok(比如gwt)，我就不能自己编写任何javascript，但我不能自己编写js。在以上述方式编写代码时，几乎在浏览器上完成的任何操作都会向ZK中的服务器发送请求。因此，最终，如果您将zk发送给服务器的请求号与gwt相比过高。我想问...

问zk对gwt zk太多的请求
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问zk对gwt zk太多的请求EN