[
https://issues.apache.org/jira/browse/AIRAVATA-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612184#comment-13612184
]
Danushka Menikkumbura commented on AIRAVATA-339:
------------------------------------------------
Based on my knowledge and prior knowledge about AMQP, RabbitMQ and Apache Qpid
have lot of potential as AMQP providers. Taking the widespread community
support into consideration, RabbitMQ looks appealing. But still the license [1]
is bit of a concern. I have not been in touch with the Qpid community lately
but they now have support for AMQP 1.0.
[1] - http://www.rabbitmq.com/mpl.html
> [GSoC] AMQP Messaging protocol support for Airavata WS-Messenger
> ----------------------------------------------------------------
>
> Key: AIRAVATA-339
> URL: https://issues.apache.org/jira/browse/AIRAVATA-339
> Project: Airavata
> Issue Type: New Feature
> Reporter: Suresh Marru
> Labels: gsoc2012, gsoc2013, mentor
>
> Airavata WS-Messenger is a Web Services-based Messaging System for
> Service-Oriented Computing and is an implementation of WS-Notification and
> WS-Eventing specifications. The message format can be automatically converted
> between the two specifications.
> With an increasing adoption of AMQP, Airavata community has interest to
> support this protocol. The subscription request type can be AMQP or
> Ws-Notification or WS-Eventing for a listener determines the message format
> that the notification consumer will receive. Currently, if WS-Notification
> subscription request is received by the broker, it will send WS-Notification
> messages to the listener. Similarly, if WS-Eventing subscription is received
> by the broker, the broker will produce WS-Eventing messages for that
> listener. The publisher can publish messages in either format. The consumers
> will receive messages in the format they subscribed irrespective of the
> format the message is published. We want to extend this functionality to
> interoperate with AMQP similarly.
> There is extensive literature about Airavata WS Messenger including 4
> research papers. The Airavata community will provide guidance and assistance
> with the project.
> User community & Impact of the software: Airavata is primarily targeted to
> build science gateways using computational resources from various
> disciplines. The initial targeted set of gateways include projects supporting
> research and education in chemistry, life sciences, biophysics, environmental
> sciences, geosciences astronomy and nuclear physics. The goal of airavata is
> to enhance productivity of these gateways to utilize cyberinfrastructure of
> resources (e.g., local lab resources, the Extreme Science and Engineering
> Discovery Environment (XSEDE), the Open Science Grid (OSG), University
> Clusters, Academic and Commercial Computational Clouds like FutureGrid &
> Amazon EC2). By using open community based software components and services
> like Airavata, gateways will be able to focus on providing additional
> scientific capabilities and to expanding the number of supported users. The
> capabilities of these gateways will offer clear benefits to society.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
