Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 3509 invoked from network); 26 Jun 2008 17:32:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jun 2008 17:32:30 -0000 Received: (qmail 78618 invoked by uid 500); 26 Jun 2008 17:32:31 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 78591 invoked by uid 500); 26 Jun 2008 17:32:30 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 78580 invoked by uid 99); 26 Jun 2008 17:32:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2008 10:32:30 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2008 17:31:40 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KBvKA-00036S-UJ for users@activemq.apache.org; Thu, 26 Jun 2008 10:31:58 -0700 Message-ID: <18139247.post@talk.nabble.com> Date: Thu, 26 Jun 2008 10:31:58 -0700 (PDT) From: alanmc To: users@activemq.apache.org Subject: Key CMS (ActiveMQ-CPP) Features Missing. Status? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: alanmc@alum.mit.edu X-Virus-Checked: Checked by ClamAV on apache.org 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.