(Update with the copy of version: 8.5.2DRAFT) |
(Update with the copy of version: 8.5.2DRAFT) |
||
| Line 1: | Line 1: | ||
= CometD= | = CometD= | ||
| − | Web Services uses version 3 | + | Web Services uses CometD version 3, 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 | + | 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 delivers messages, providing clients with a consistent approach while maintaining support for multiple browsers. |
{{NoteFormat|Web Services and Applications does not currently support web sockets.}} | {{NoteFormat|Web Services and Applications does not currently support web sockets.}} | ||
Latest revision as of 16:41, July 14, 2017
CometD
Web Services uses CometD version 3, 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 delivers 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.
This page was last edited on July 14, 2017, at 16:41.
Comments or questions about this documentation? Contact us for support!