ZK vs. GWT : Server-Centric Matters!
[ Jeff Liu is an engineer with Potix Corporation, who are creators of the ZK framework ]
Server-Centric and Client-Centric
- Where Applications Run
- Server and Client Centric Ajax Frameworks in Practice: ZK and GWT
- ZK vs. GWT in Action : Google Maps Locator
- ZK (1 File, 36 Lines of Code)
- GWT (5 Files, 190 Lines of Code)
- DWR (2 Files, 77 Lines of Code)
ZK vs. GWT in Action 2 : Data-binding
- ZK (1 File, 39 Lines of Code)
- GWT (4 Files, 200 Lines of code)
ZK vs. GWT in Action 3 : Live data
- ZK (1 File, 15 Lines of Code)
- GWT (I Don Even Want to Code It)
- What about the devices without browsers?
- ZK on Java Phones
- ZK on Google Android
- Right Tool for the Right Job
2. Server-Centric and Client-Centric
Where Applications Run:
In short, the main difference between server-centric and client-centric is where the application runs. In a server-centric framework, the application is hosted on the application server and all processing is done on the server. The client browser is only used for data presentation.
so security compromises that exploit client-side state and logic are more difficult to pull off.
The developers can work in one language (on the server) and, for the most part,
ignore the fact they are writing a web application.?/cite>
- by Dietrich Kappe, Chief Technology Officer of Pathfinder
To Know more how ZK works as a server-centric framework, refer to the following:
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)