Tags
People
Badges
Help-
CORE FRAMEWORK
FEATURED COMPONENTS
-
RESOURCES
-
LEARN ZK
RESOURCES
Hello,
I want to use ZK server push. Design pattern will be MVVM. ZK version is 8.6.1. I will have 500-1000 active ZK desktops at any moment in almost the same number of sessions. When I receive request (for example refresh current listbox or delete some list item), I have to do some operation. What is preferred way to do this based on number of desktops? Standard server push or Web sockets?
I found it inside ZATS documentation: https://www.zkoss.org/wiki/ZATS%20Essentials/Mimic%20Library/Operation/PollingAgent
Based on documentation, PoolingAgent was introduced with 1.2.1 version. How we can test server push?
I tried to find PoolingAgent in the history of ZATS, it didn't exist in 1.2.0 or 1.0.0 inside our github repo.
Can you please specify where you found it before 2.0.0, or where it was removed in the git history - just to speed up the search.
"Standard" server push use individual HTTP requests - either comet (long polling) or interval polling. Those requests produce overhead in addition to the "normal" /zkau requests for transporting the events and dynamic updates of a desktop. If you can use websockets, serverpush, events and dynamic updates use the same connection only established once. So in theory websockets should be lean choice, if available. (Still websockets is not fully adopted in all environments/application servers, so you'll have to test whether they perform well or work at all for your customers, ZK will fallback to ajax in case a websocket connection can't be established).
MVC/MVVM doesn't matter in this case, events from client and updates to the server are equivalent for both patterns.
Asked: 2020-05-28 21:43:13 +0800
Seen: 22 times
Last updated: Jun 03 '20
