Server Push"
m |
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 Queues| | + | No matter which implementation you choose, the use is the same. The [[ZK Developer's Reference/Server Push/Event Queues|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/Asynchronous Tasks|Asynchronous Tasks]] and [[ZK Developer's Reference/Server Push/Synchronous Tasks|Synchronous Tasks]] sections, depending on whether you task can be executed asynchronously. |
{{ZKDevelopersReferenceHeadingToc}} | {{ZKDevelopersReferenceHeadingToc}} | ||
Revision as of 05:51, 23 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 -- it is also called Ajax Push. These approaches could be summarized to two categories, 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 Asynchronous Tasks and Synchronous Tasks sections, depending on whether you task can be executed asynchronously.
- ↑ More precisely, it is so-called long polling.