You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by astitcher <as...@apache.org> on 2014/06/23 21:04:11 UTC

[Announcement] CMS for AMQP 1.0

Over the past few months I've been working on an implementation of CMS (that
is the JMS like C++ library for messaging) that uses the AMQP 1.0 as its
underlying transport protocol.

This implementation is still in its early stages and is a separate
implementation from the original CMS library. It has the same interface and
this is ensured by using the same header files which are currently included
in the git repository by using the existing ActiveMQ CMS git mirror as a
submodule.

This implementation uses the Apache Qpid Messaging C++ client for the AMQP
protocol support, and so you will need Apache Qpid and Apache Qpid Proton to
build this version of CMS (at least 0.28 for Qpid Messaging and 0.7 for Qpid
Proton). 

Incidentally the reason this is a new implementation and doesn't try to plug
into the multi-protocol support in the existing CMS library is that the
interfaces there seem to be very tied into the way that the ActiveMQ Java
code was ported to C++, and hard to introduce an external library to.
Additionally the Qpid Messaging C++ API is already a similar connection
oriented API to JMS/CMS and seemed like an efficient starting place.

Being in its early stages there are pieces missing, however many features
are supported and I think it is useful enough to evaluate. To see what is
still missing look at TODO.md in the top level of the source tree.

Note that one large difference between this implementation and the ActiveMQ
CMS implementation is that I provide no lower level utility libraries akin
to the Java libraries (the activemq and decaf namespaces)

I would be grateful to know what is still needed to make the library useful
for people to use.

Currently I am hosting this work from my github account and you can clone or
fork it from there:
    https://github.com/astitcher/qpid-cms

Any feedback, question, ideas, opinions etc. will be gratefully received.
(either to me directly or reply to this mailing list thread)

Thanks

Andrew




--
View this message in context: http://activemq.2283324.n4.nabble.com/Announcement-CMS-for-AMQP-1-0-tp4682401.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: [Announcement] CMS for AMQP 1.0

Posted by Gordon Sim <gs...@redhat.com>.
Forwarded from activemq user list in case anyone on this list hasn't 
seen it and is interested:

On 06/23/2014 08:04 PM, astitcher wrote:
> Over the past few months I've been working on an implementation of CMS (that
> is the JMS like C++ library for messaging) that uses the AMQP 1.0 as its
> underlying transport protocol.
>
> This implementation is still in its early stages and is a separate
> implementation from the original CMS library. It has the same interface and
> this is ensured by using the same header files which are currently included
> in the git repository by using the existing ActiveMQ CMS git mirror as a
> submodule.
>
> This implementation uses the Apache Qpid Messaging C++ client for the AMQP
> protocol support, and so you will need Apache Qpid and Apache Qpid Proton to
> build this version of CMS (at least 0.28 for Qpid Messaging and 0.7 for Qpid
> Proton).
>
> Incidentally the reason this is a new implementation and doesn't try to plug
> into the multi-protocol support in the existing CMS library is that the
> interfaces there seem to be very tied into the way that the ActiveMQ Java
> code was ported to C++, and hard to introduce an external library to.
> Additionally the Qpid Messaging C++ API is already a similar connection
> oriented API to JMS/CMS and seemed like an efficient starting place.
>
> Being in its early stages there are pieces missing, however many features
> are supported and I think it is useful enough to evaluate. To see what is
> still missing look at TODO.md in the top level of the source tree.
>
> Note that one large difference between this implementation and the ActiveMQ
> CMS implementation is that I provide no lower level utility libraries akin
> to the Java libraries (the activemq and decaf namespaces)
>
> I would be grateful to know what is still needed to make the library useful
> for people to use.
>
> Currently I am hosting this work from my github account and you can clone or
> fork it from there:
>      https://github.com/astitcher/qpid-cms
>
> Any feedback, question, ideas, opinions etc. will be gratefully received.
> (either to me directly or reply to this mailing list thread)
>
> Thanks
>
> Andrew


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org