| 12 | | All funtions offered by QCG-Notification can be invoked using different transport protocols. Currently, our system supports the SOAP communication over HTTP, HTTPS, and additionally XMPP. Thanks to the XMPP based communication, all notification parties, namely Subscribers, Publishers, Notification Consumers and QCG-Notification itself, can be located behind firewalls with only well defined outgoing TCP/IP port open for the XMPP transport communication. |
| | 12 | All funtions offered by QCG-Notification can be invoked using different transport protocols. Currently, our system on a server side supports the SOAP communication over HTTP, HTTPS, and XMPP. The client side (publisher side) of QCG-Notification is based on dynamically loaded plugins. QCG-Notification offers here SOAP over HTTP, HTTPS and XMPP as well as SMTP (e-mail). Thanks to the XMPP based communication, all notification parties, namely Subscribers, Publishers, Notification Consumers and QCG-Notification itself, can be located behind firewalls with only well defined outgoing TCP/IP port open for the XMPP transport communication. |
