Currently ActiveMQ has several C/C++ clients (with another client library waiting to get through the donator's lawyers), so it might make sense at some point to try unify the C++ clients together too so users have a single C++ API for their messaging client and then a number of implentations/transports/protocols to use at deployment time. i.e. making a JMS for C++ API. (We've got a good start called CMS in ActiveMQ...)
I agree that a C++ (and also C) rendering of a JMS like API is going to be a very useful thing. James - do you have any idea how CMS matches or differs from IBM's XMS (http://www-128.ibm.com/developerworks/websphere/library/techarticles/0509_phillips/0509_phillips.html)? XMS is also a rendering of JMS into C/C#/C++. I think it would be interesting to see a confluence of the APIs and protocols between ActiveMQ and Blaze giving interoperability in both code and on the wire. Paul
http://incubator.apache.org/activemq/activemq-cpp-client.html -- James ------- http://radio.weblogs.com/0112098/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
