Changes between Initial Version and Version 1 of features

Show
Ignore:
Timestamp:
07/23/12 10:25:42 (12 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • features

    v1 v1  
     1From the architecture perspective, QCG-Notification exposes a well-defined Web Service interface corresponding to the role of Notification Broker as well as it offers other standard interfaces for managing Subscriptions and Pull Points. 
     2It supports advanced two-layer notification filtering based on hierarchical topic namespaces and XPath queries on the content of messages.   
     3 
     4All 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. In turn, the client side (Publisher side) of the system is based on dynamically loaded plugins. Currently QCG-Notification offers here SOAP over HTTP, HTTPS and XMPP as well as SMTP (e-mail) protocol. 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. 
     5 
     6 
     7[[Image(QCG-Notification-Architecture-v2.png,400px,center)]]