You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2013/10/18 16:34:44 UTC

[jira] [Created] (AMQNET-454) Add Apache Qpid provider to NMS

Chuck Rolke created AMQNET-454:
----------------------------------

             Summary: Add Apache Qpid provider to NMS
                 Key: AMQNET-454
                 URL: https://issues.apache.org/jira/browse/AMQNET-454
             Project: ActiveMQ .Net
          Issue Type: New Feature
          Components: NMS
    Affects Versions: 1.6.0
            Reporter: Chuck Rolke
            Assignee: Jim Gomes


NMS includes various providers ActiveMQ, STOMP, MSMQ, EMS, and WCF. This issue proposes to add [Apache Qpid|http://qpid.apache.org/index.html] as another provider.

Qpid has a [Messaging .NET Binding|http://qpid.apache.org/releases/qpid-0.24/programming/book/ch05.html] that is layered on top of the native C++ Qpid Messaging client. The Qpid .NET binding is attractive as the hook for tying in Qpid as an NMS provider.

The proposed NMS provider supports [AMQP 1.0|http://qpid.apache.org/amqp.html] by including [Qpid Proton|http://qpid.apache.org/proton/index.html] libraries.

>From a high level this addition to Active.NMS would consist of two parts
* Add Qpid as a vendor kit. This includes both the Qpid .NET Binding and Qpid Proton in a single kit.
* Add the new provider with code linking NMS to Qpid





--
This message was sent by Atlassian JIRA
(v6.1#6144)