Line 1: | Line 1: | ||
= CometD= | = CometD= | ||
− | + | Web Services uses version 3 of CometD, 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. | |
− | + | Web Services uses CometD to deliver unsolicited notifications to clients for real-time events, such as getting a new call or chat message. At runtime, CometD uses the best technology available to deliver messages, providing clients with a consistent approach while maintaining support for multiple browsers. | |
− | {{NoteFormat| | + | {{NoteFormat|Web Services and Applications does not currently support web sockets.}} |
<!--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 details about CometD, see [http://cometd.org/ http://cometd.org/]. | For details about CometD, see [http://cometd.org/ http://cometd.org/]. | ||
− | For details about how to configure CometD in | + | For details about how to configure CometD in Web Services, see [[HTCCConfigurationOptionsReference#cometDSettings|cometDSettings]]. |
[[Category:V:HTCC:8.5.2DRAFT]] | [[Category:V:HTCC:8.5.2DRAFT]] |
Revision as of 14:39, December 9, 2015
CometD
Web Services uses version 3 of CometD, 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.
Web Services uses CometD to deliver unsolicited notifications to clients for real-time events, such as getting a new call or chat message. At runtime, CometD uses the best technology available to deliver messages, providing clients with a consistent approach while maintaining support for multiple browsers.
Important
Web Services and Applications does not currently support web sockets.For details about CometD, see http://cometd.org/.
For details about how to configure CometD in Web Services, see cometDSettings.
Comments or questions about this documentation? Contact us for support!