ZK Developer's Reference/Server Push/Synchronous Tasks

Server push is a technology to actively push data to the client. For ZK, the data is usually the UI updates or its variants. Thus, for the sake of understanding, we could consider the task to be about updating UI in parallel with regular Ajax requests (poll-type requests). For example, in a chat application, once a message is entered by a participant, the server has to push it to all clients that are involved in the conversation.

If the task of updating UI takes place in a working thread, it is generally more convenient to execute it synchronously as described later. On the other hand, if the task can be encapsulated as an event listener (EventListener), you could execute it asynchronously -- please refer to the Asynchronous Tasks section for more information.

Enable Server Push

By default, the server push is disabled (for better performance). Before pushing data for a given desktop, you have to enable the server push for it.

It can be done by use of Desktop.enableServerPush(boolean):

desktop.enableServerPush(true);

After the server push of a given desktop is enabled, you could use any number of working threads to update the desktop concurrently as described in the following section.

---

Update UI in a Working Thread

To update the UI synchronously in a working thread, we have to do as follows.

1. Invoke Executions.activate(Desktop). It has two purposes:
   1. It grants the right to access the UI of the given desktop to the caller's thread.

      Notice that, for each desktop, at most one thread is allowed to access at the same time.

   2. It establishes a connection with the client (the browser window displaying the desktop), such that the update will be sent to the client after finished.
2. Update UI any way you want, just like any regular event listener.
3. Invoke Executions.deactivate(Desktop) to return the control, such that other threads could have a chance to update UI.

Here is an example code that illustrates the usages:

 1 public class WorkingThread extends Thread {
 2     public void run() {
 3         try {
 4             while (anyDataToShow()) {
 5                 //Step 1. Prepare the data that will be updated to UI
 6                 collectData(); //prepare the data to set to components
 7 
 8                 //Step 2. Activate to grant the access of the given desktop
 9                 Executions.activate(desktop);
10                 try {
11                      //Step 3. Update UI
12                      updateUI(); //implement the logic to change UI, call ZK component API or notify change
13                 } finally {
14                     //Step 4. Deactivate to return the control of UI back
15                      Executions.deactivate(desktop);
16                 }
17             }
18         } catch (InterruptedException ex) {
19             //Interrupted. You might want to handle it
20         }
21     }
22 
23    /**
24      * To update UI you can do one of the followings:
25      * - to notify changes with {@link BindUtils#postNotifyChange(Object, String)} if changing a ViewModel's property
26      * - call a component's setter
27      * - If calling a {@link org.zkoss.zul.ListModel} method, it automatically updates for you without notifying
28      */
29     protected void updateUI() {
30         data.clear();
31         data.add("now " + System.currentTimeMillis());
32     }
33 }

• Line 9-15: the task between Executions.activate(Desktop) and Executions.deactivate(Desktop) has to take less time, since it blocks others, including the end users (of the desktop), from accessing the UI. It is suggested to prepare the data before Executions.activate(Desktop), such that it can be done in parallel with other threads.

For a real example, please refer to small talks: Simple and Intuitive Server Push with a Chat Room Example and Server Push with a Stock Chart Example.

Version History

Version	Date	Content