Server Push"

From Documentation
(Created page with '{{ZKDevelopersReferencePageHeader}} HTTP is a request-and-response protocol. Technically, there is no way to have the server to actively ''push'' data to the client. However, th…')
 
m
Line 5: Line 5:
 
Different approaches have different pros and cons, and we discuss them in the [[ZK Developer's Reference/Server Push/Configuration|Configuration]] section.
 
Different approaches have different pros and cons, and we discuss them in the [[ZK Developer's Reference/Server Push/Configuration|Configuration]] section.
  
No matter which implementation you choose, the use is the same. [[ZK Developer's Reference/Server Push/Event Queue|The Event Queue]] is the high-level API, and the suggested approach for its simplicity. However, if you prefer to access the low-level API directly, you could refer to the [[ZK Developer's Reference/Server Push/Synchronous Task|Synchronous Task]] and [[ZK Developer's Reference/Server Push/Asynchronous Task|Asynchronous Task]] sections, which are two sets of low-level for tasks that can be executed either synchronously or asynchronously.
+
No matter which implementation you choose, the use is the same. [[ZK Developer's Reference/Server Push/Event Queues|The Event Queue]] is the high-level API, and the suggested approach for its simplicity. However, if you prefer to access the low-level API directly, you could refer to the [[ZK Developer's Reference/Server Push/Synchronous Tasks|Synchronous Tasks]] and [[ZK Developer's Reference/Server Push/Asynchronous Tasks|Asynchronous Tasks]] sections, which are two sets of low-level for tasks that can be executed either synchronously or asynchronously.
  
 
{{ZKDevelopersReferenceHeadingToc}}
 
{{ZKDevelopersReferenceHeadingToc}}

Revision as of 10:36, 22 November 2010

HTTP is a request-and-response protocol. Technically, there is no way to have the server to actively push data to the client. However, there are a few approaches to emulate push. They could be summarized to two approaches, client polling and comet[1], that are both supported.

Different approaches have different pros and cons, and we discuss them in the Configuration section.

No matter which implementation you choose, the use is the same. The Event Queue is the high-level API, and the suggested approach for its simplicity. However, if you prefer to access the low-level API directly, you could refer to the Synchronous Tasks and Asynchronous Tasks sections, which are two sets of low-level for tasks that can be executed either synchronously or asynchronously.




  1. More precisely, it is so-called long polling.


Last Update : 2010/11/22

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.