activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Mittler" <>
Subject Re: Recommended C/C++ client
Date Mon, 12 Feb 2007 20:24:03 GMT
Hi Juan,
The c/c++ client with the most active development is activemq-cpp (  Version 1.1 has just
been released (although we haven't yet updated the links on the download

For example usage of the client, go here:

The 1.1 version only supports the stomp protocol, but we're actively working
on openwire support for 2.0 and already have some parts working.  The great
part about this client is that switching between stomp and openwire is
transparent to the API, so when we finally get the openwire support nailed
down, your client will not have to change to migrate to openwire.

Stomp is a simple text-based protocol that implements a subset of the
features of JMS.  ActiveMQ has its own extensions which help to add some of
the functionality that stomp is missing.  It should be known that the
limitations in the stomp protocol create some quirks in the stomp support
that you may want to be aware of, documented here:

Apart from that, openwire is a high-performance protocol and is the native
protocol used by the ActiveMQ broker.  So once activemq-cpp solidifies the
openwire support, the performance should go up significantly.


On 2/12/07, Juan Jose Comellas <> wrote:
> Hi, I'm new to the list and to ActiveMQ. I'm starting a project where
> several C and Java distributed processes will have to communicate
> among themselves and I wanted to use ActiveMQ for it.
> I've seen there are several C/C++ interfaces and I wanted to know
> which one is the recommended one. One of my applications is written in
> C and I would prefer to use a C library for it, but only if it's not a
> major pain compared to the C++ interface (I could always wrap the C++
> code with some C interfaces). Also, it's not clear to me whether I
> should use the Stomp or the Openwire clients? What are the pros/cons
> of each of these libraries.
> BTW, if there is a FAQ or some documentation where all my questions
> have already been answered I'd appreciate if somebody could point me
> to it.
> Thanks in advance.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message