Hi,
as a Java programmer who needs to write a wrapper around ActiveMQ-CPP in C++, I am of course very happy to see familiar concepts such as "synchronized()" available as part of the "decaf" namespace under ActiveMQ-CPP 2.2. Indeed, when mixing threads between ActiveMQ and my code, I guess it is a good idea to use the same threading mechanism as ActiveMQ, so reusing the stuff from decaf::util::concurrent seems like the right thing to do. So here is my question: How stable can I expect the 'decaf' API to be? Is it safe for me to use this, i.e., can I hope that changes to the decaf API in future versions of ActiveMQ-CPP will be backward-compatible? I am asking because of the incompatible API change between ActiveMQ-CPP 2.1 and 2.2. Thanks for this nice piece of software, and best regards, Marc -- View this message in context: http://www.nabble.com/Using-decaf-API-in-user-code--tp19436487p19436487.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
