| Line 2: | Line 2: | ||
__NOTOC__ | __NOTOC__ | ||
==Overview== | ==Overview== | ||
| − | Genesys Web Services uses version 3 of CometD. | + | Genesys Web Services uses version 3 of CometD. CometD is an HTTP-based routing bus that uses an Ajax Push technology pattern known as Comet. Comet is a web application model that allows an HTTP request to push data to a browser, even if the browser has not requested it. |
| − | CometD | + | Genesys Web Services uses CometD to deliver unsolicited notifications to clients for realtime events, such as getting a new call or chat message. At runtime, CometD will use the best technology available to deliver messages, providing clients with a consistent approach while maintaining support for multiple browsers. |
| − | + | For example: | |
| − | + | If the browser supports websockets, the websocket transport would be selected when the connection is negotiated. If the browser does not support websockets, other techniques such as long polling can be used to provide the same result. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | For example: If the browser supports websockets, the websocket transport would be selected when the connection is negotiated. If the browser does not support websockets, other techniques such as long polling can be used to provide the same result. | ||
For more details about CometD, see [http://cometd.org/ http://cometd.org/]. | For more details about CometD, see [http://cometd.org/ http://cometd.org/]. | ||
[[Category:V:HTCC:8.5.2DRAFT]] | [[Category:V:HTCC:8.5.2DRAFT]] | ||
Revision as of 17:03, August 26, 2014
CometD
Overview
Genesys Web Services uses version 3 of CometD. CometD is an HTTP-based routing bus that uses an Ajax Push technology pattern known as Comet. Comet is a web application model that allows an HTTP request to push data to a browser, even if the browser has not requested it.
Genesys Web Services uses CometD to deliver unsolicited notifications to clients for realtime events, such as getting a new call or chat message. At runtime, CometD will use the best technology available to deliver messages, providing clients with a consistent approach while maintaining support for multiple browsers.
For example: If the browser supports websockets, the websocket transport would be selected when the connection is negotiated. If the browser does not support websockets, other techniques such as long polling can be used to provide the same result.
For more details about CometD, see http://cometd.org/.