Changes between Version 12 and Version 13 of WikiStart

Show
Ignore:
Timestamp:
06/03/11 11:44:07 (13 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v12 v13  
    66 
    77== Installation == 
    8 Please refer to the [http://apps.man.poznan.pl/trac/qcg-notification/downloads Downloads] section to get the most recent QCG-Notification packages (cf. [http://apps.man.poznan.pl/trac/qcg-notification/wiki/Changelog Changelog]) and corresponding Software Development Kits (SDKs). The installation procedure is presented in the doc directory of the QCG-Notification package. 
     8Please refer to the [http://apps.man.poznan.pl/trac/qcg-notification/downloads Downloads] section to get the most recent QCG-Notification packages (cf. [http://apps.man.poznan.pl/trac/qcg-notification/wiki/Changelog Changelog]) and corresponding Software Development Kits (SDKs). The QCG-Notification manual distributed in the doc directory of QCG-Notification package provides detailed information about installation and configuration procedures. If you want to deploy entire QosCosGrid stack you may also follow [[/wiki/installation|QCG-Notification installation]] to proceed basic steps needed to use the QCG-Notification within QosCosGrid.  
    99 
    1010== Features == 
    1111From 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. 
    1212 
    13 All funtions offered by Smoa 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 Smoa Notification itself, can be located behind firewalls with only well defined outgoing TCP/IP port open for the XMPP transport communication. 
     13All 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. 
    1414 
    1515The following list summarizes all major concepts defined in the WS-Notification documents and adopted by QCG-Notification: