Changes between Version 2 and Version 3 of WikiStart

Show
Ignore:
Timestamp:
05/25/11 14:35:50 (13 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v2 v3  
    1 = Smoa Notification = 
     1= QCG-Notification = 
    22 
    3 Smoa Notification is an open source implementation of the family of WS-Notification standards (Base Notification, Brokered Notification and Topics). It supports the topic-based publish/subscribe pattern for the asynchronous message exchange among Web Services and other involved entities. The main architecture of our system is based on a highly efficient, extended version of the Notification Broker, managing all items participating in notification events. Today, Smoa Notification offers sophisticated notification capabilities, e.g. notification message filtering, push and pull messages delivery, and it was successfully integrated with different communication protocols as well as various Web Services security mechanisms. The modular architecture of Smoa Notification also provides a great opportunity for developers to build new extensions and plugins to meet other specific requirements. 
     3QCG-Notification is an open source implementation of the family of WS-Notification standards (Base Notification, Brokered Notification and Topics). It supports the topic-based publish/subscribe pattern for the asynchronous message exchange among Web Services and other involved entities. The main architecture of our system is based on a highly efficient, extended version of the Notification Broker, managing all items participating in notification events. Today, QCG-Notification offers sophisticated notification capabilities, e.g. notification message filtering, push and pull messages delivery, and it was successfully integrated with different communication protocols as well as various Web Services security mechanisms. The modular architecture of QCG-Notification also provides a great opportunity for developers to build new extensions and plugins to meet other specific requirements. 
    44 
    55== Installation == 
    6 Please refer to the [http://apps.man.poznan.pl/trac/smoa-ntf/downloads Downloads] section to get the most recent Smoa Notification packages (cf. [http://apps.man.poznan.pl/trac/smoa-ntf/wiki/Changelog Changelog]) and corresponding Software Development Kits (SDKs). The installation procedure is presented in the doc directory of the Smoa Notification package. 
     6Please 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. 
    77 
    88[[Image(architecture2.png,500px,center)]] 
    … …  
    1010== Features == 
    1111 
    12 From the architecture perspective, Smoa 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. 
     12From 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. 
    1313 
    1414All 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. 
    1515 
    16 The following list summarizes all major concepts defined in the WS-Notification documents and adopted by Smoa Notification: 
     16The following list summarizes all major concepts defined in the WS-Notification documents and adopted by QCG-Notification: 
    1717* Situation 
    1818* Notification 
    … …  
    3030== Performance == 
    3131 
    32 The low-level architecture of Smoa Notification is based on highly efficient mechanisms and data structures. In performed tests we sent 1000 notification messages via different WS-Notification implementations. The obtained results clearly show that Smoa Notification outperforms competitors. 
     32The low-level architecture of QCG-Notification is based on highly efficient mechanisms and data structures. In performed tests we sent 1000 notification messages via different WS-Notification implementations. The obtained results clearly show that QCG-Notification outperforms competitors. 
    3333 
    3434[[Image(test-1.png, 600px, center)]] 
    … …  
    3636== Related software == 
    3737 
    38 * Smoa Core - generic library must be installed in the system in prior to the installation of Smoa Notification. 
    39 * Smoa XMPP - plugins for Pidgin may be utilized for enabling WS-Notifications in the popular XMPP communicator. 
     38* QCG-Core - generic library must be installed in the system in prior to the installation of QCG-Notification. 
     39* QCG-XMPP - plugins for Pidgin may be utilized for enabling WS-Notifications in the popular XMPP communicator. 
    4040 
    4141== Applications == 
    42 * CosQosGrid - In this projectd Smoa Notification together with other Web Services using the Smoa framework, in particular Smoa Computing, was used to build highly efficient grid middleware for cross-cluster parallel application execution and monitoring. 
    43 * BREIN - Smoa Notification was demonstrated in asynchronous and dynamic message exchange in a distributed IT system controlling some events generated by an example airport management system, such as flight delays, SLA violations, etc. 
    44 * PL-Grid - Smoa Notification is going to be productively used under the national grid infrastructure initiative in Poland. 
     42* QosCosGrid - In this projectd QCG-Notification together with other Web Services using the QosCosGrid framework, in particular QCG-Computing, was used to build highly efficient grid middleware for cross-cluster parallel application execution and monitoring. 
     43* BREIN - QCG-Notification was demonstrated in asynchronous and dynamic message exchange in a distributed IT system controlling some events generated by an example airport management system, such as flight delays, SLA violations, etc. 
     44* PL-Grid - QCG-Notification is going to be productively used under the national grid infrastructure initiative in Poland. 
     45* Mapper - In the Mapper project, QosCosGrid stack is exploited to perform multiscale computations on EGI and PRACE resources.