Changes between Version 2 and Version 3 of features

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

--

Legend:

Unmodified
Added
Removed
Modified
  • features

    v2 v3  
    66All 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. 
    77 
     8[[Image(QCG-Notification-Architecture-v2.png,400px,center)]] 
    89 
    9 [[Image(QCG-Notification-Architecture-v2.png,400px,center)]] 
     10The low-level architecture of QCG-Notification is based on highly efficient mechanisms and data structures. We compared the three notification systems that confirmed the good performance of our sollution. See [[wiki/benchmarks|Benchmarks]] for details.