RE: AMQ production status
Comments inline: > > >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. > > We are using the main.cpp file that comes in /test along with the Stomp > C++ > APIs from svn : > https://svn.apache.org/repos/asf/incubator/activemq/trunk/cms. We have > segregated the main.cpp into a sender and a receiver. > > 1) From where can I get the fresh CMS replacement as told by you. Can you > provide the specific location? The CMS replacement is called activemq-cpp and its located here: https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-cpp It is still under active development by Nathan and me. > > > >I would try activemq-cpp, if you haven't already - it's leaps and bounds > >above the old CMS code! > > 2) I am using ActiveMQ 4.0.x java version. Is activemq-cpp a C++ MQ > server? > If, then what's its capacity against Java, .Net clients. Activemq-cpp is a c++ implementation of the JMS Client API, currently it only speaks the stomp protocol, but in time it should also gain the ability to use the openwire protocol as well. You still need to run an AMQ broker just as you did before. The tests in the test-integration folder show example usage, which is now very much like using the Java based JMS client API. - Timothy A. Bish Sensis Corporation -
RE: AMQ production status
Hi Nate Thanks for the information. 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. We are using the main.cpp file that comes in /test along with the Stomp C++ APIs from svn : https://svn.apache.org/repos/asf/incubator/activemq/trunk/cms. We have segregated the main.cpp into a sender and a receiver. 1) From where can I get the fresh CMS replacement as told by you. Can you provide the specific location? I would try activemq-cpp, if you haven't already - it's leaps and bounds above the old CMS code! 2) I am using ActiveMQ 4.0.x java version. Is activemq-cpp a C++ MQ server? If, then what's its capacity against Java, .Net clients. Hearty Regards Naveen Rawat
RE: AMQ production status
Hi Naveen, Comments inline ... > -Original Message- > From: Naveen Rawat [mailto:[EMAIL PROTECTED] > 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
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). 1) Are both these C++ APIs (Stomp and Openwire) worth implementation and usage right now, or they are being made more ROBUST? 2) When can we see a PRODUCTION-able AMQ along with its full throttled APIs? Hearty Regards Naveen Rawat
