activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mittler, Nathan" <nathan.mitt...@sensis.com>
Subject RE: AMQ production status
Date Thu, 06 Jul 2006 12:02:21 GMT
Hi Naveen,
Comments inline ...

> -----Original Message-----
> From: Naveen Rawat [mailto:naveen@in.effectsoft.com] 
> Sent: Thursday, July 06, 2006 7:48 AM
> To: activemq-dev@geronimo.apache.org
> Subject: AMQ production status
> 
> 
> Hi James 
> 
> 
> We have our servers in C/C++. We are trying out available 
> open source MQ services for maintaining persistent 
> communication with our servers through our C++ and web clients. 
> 
> We tried the tests available for both Stomp and Openwire and 
> got very little success with Stomp C++ (caught up with the 
> persistency issue) and considerable with openwire C++ (I have 
> an issue regarding this mailed to the mailing list on 06-July-2006). 

Just out of curiosity, which Stomp C++ client did you try?  The reason I
ask is that we just submitted a replacement for the CMS client in
activemq-cpp. This API does appear to have support for persistence,
although I'm not sure that we have a unit test that verifies it yet.

> 
> 1) Are both these C++ APIs (Stomp and Openwire) worth 
> implementation and usage right now, or they are being made 
> more ROBUST? 
> 

The activemq-cpp is new and will be the beginning of creating a single
C++ client that will support both stomp and openwire (you will be able
to choose which protocol in the url).  So, there is definitely activity
in this area and they should continue to improve.

> 2) When can we see a PRODUCTION-able AMQ along with its full 
> throttled APIs? 
> 

I would try activemq-cpp, if you haven't already - it's leaps and bounds
above the old CMS code!

>  
> 
> 
> Hearty Regards
> Naveen Rawat
> 

Regards,
Nate

Mime
View raw message