The missing features are things that would be nice to add, but so far there has not been enough time for us to do so, we'd definitely welcome contributions to the project.
There is currently an issue for creating a Failover Transport but so far there is nobody working on it. http://issues.apache.org/activemq/secure/IssueNavigator.jspa?reset=true&; mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=1100 0&fixfor=11866 For discovery I'd imagine that we'd need to add a UDP transport and the necessary plumbing for the discovery portion. You could create an issue in Jira to add this if you'd like, but again with limited resources the fastest way to get this in would be for someone to step up and contribute it. Regards Tim. > -----Original Message----- > From: alanmc [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2008 10:32 AM > To: users@activemq.apache.org > Subject: Key CMS (ActiveMQ-CPP) Features Missing. Status? > > > We are using ActiveMQ-CPP to build a massively scalable SOA and have been > happy with the product so far, however CMS is missing some key features, > namely Failover and Discovery. Those two features seem to be necessary > for > delivering production-quality components using CMS. Are those features > actively being worked on? Would Discovery first require implementing a > UDP > or multicast protocol for CMS? Just trying to figure out if these > features > are already on the roadmap or if you need a contributor to take a crack at > these. I poked around at the java implementation of Failover and may be > able to take a shot at a rough port of that. > > Also, is it possible for a C++ client to connect to a network of brokers > over TCP? > -- > View this message in context: http://www.nabble.com/Key-CMS-%28ActiveMQ- > CPP%29-Features-Missing.--Status--tp18139247p18139247.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
