An Introduction to ZK's Server client Fusion Architecture"
| Line 3: | Line 3: | ||
[[Image:architecture-s.png]] | [[Image:architecture-s.png]] | ||
| − | A ZK application runs | + | A ZK application runs on the server. It could access the backend resources, assemble UI with components, listen to user's activity, and then manipulate components to update UI. All are done at the server. The synchronization of the states of the components between the browser and the server is done automatically by ZK, awhich is also transparent to the application. |
| − | When running at the server, the application can access the full stack of Java technology. User activities | + | When running at the server, the application can access the full stack of Java technology. User activities, including Ajax and Server Push, are abstracted to event objects. UI are composed of POJO-like components. It is the most productive approach to develop a modern Web application. |
| − | With ZK's Server+client Fusion architecture, your application won't stop at the server. The application could enhance the interactivity by adding optional client-side functionality, such as client-side event handling, visual effect customizing, and even UI composing without the server-side code. ZK enables the seamless fusion | + | With ZK's Server+client Fusion architecture, your application won't stop at the server. The application could enhance the interactivity by adding optional client-side functionality, such as client-side event handling, visual effect customizing, and even UI composing without the server-side code. ZK enables the seamless fusion from pure server-centric to pure client-centric. You could have the best of two worlds: productivity and flexibility. |
{{ZKEssentialsPageFooter}} | {{ZKEssentialsPageFooter}} | ||
Revision as of 01:54, 22 June 2011
This article is out of date, please refer to http://books.zkoss.org/zkessentials-book/master/ for more up to date information.
A ZK application runs on the server. It could access the backend resources, assemble UI with components, listen to user's activity, and then manipulate components to update UI. All are done at the server. The synchronization of the states of the components between the browser and the server is done automatically by ZK, awhich is also transparent to the application.
When running at the server, the application can access the full stack of Java technology. User activities, including Ajax and Server Push, are abstracted to event objects. UI are composed of POJO-like components. It is the most productive approach to develop a modern Web application.
With ZK's Server+client Fusion architecture, your application won't stop at the server. The application could enhance the interactivity by adding optional client-side functionality, such as client-side event handling, visual effect customizing, and even UI composing without the server-side code. ZK enables the seamless fusion from pure server-centric to pure client-centric. You could have the best of two worlds: productivity and flexibility.