Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 41341 invoked from network); 18 Jun 2008 22:20:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jun 2008 22:20:11 -0000 Received: (qmail 50461 invoked by uid 500); 18 Jun 2008 22:20:11 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 50429 invoked by uid 500); 18 Jun 2008 22:20:11 -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 50417 invoked by uid 99); 18 Jun 2008 22:20:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2008 15:20:10 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rajdavies@gmail.com designates 66.249.92.170 as permitted sender) Received: from [66.249.92.170] (HELO ug-out-1314.google.com) (66.249.92.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2008 22:19:18 +0000 Received: by ug-out-1314.google.com with SMTP id u2so885562uge.5 for ; Wed, 18 Jun 2008 15:19:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=cJ/HPRc17EXPev0dDHw8CdcNPP52WQMWP5pb+xgbQvo=; b=V9aAOf8CIv/4oCNm4iGi/tI33juytThJvlADuJZYd3nixZAgEe1Fa7XwR1uvGMnis1 WOWEcUCv6G8pkY7JGMFrdaR1HAy0eU1i0PGvTBm5Zeq8tg8TDTnatX90bs3kEZGsdnzc RAUz+ZNpyI8NB09QbEqeUtvhwcI8lRSx9yGU8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=aLKQE2wc1LeISeliXuaH4mgjZ0WZLiwnaDtv6+MKoF5yI5SgsYa3t5PzjDRuHZzPR1 bSfMW46OfvAsGdy5hVOv1OlYfYsXmzG1PRTRqHRD+RR9De+mRTWQCxCxMVgtF9O+wQ6G fgd15Qb0b5mrNbGaF3PPJcMtrZMP6dU7/1sB0= Received: by 10.210.46.12 with SMTP id t12mr1114939ebt.64.1213827575178; Wed, 18 Jun 2008 15:19:35 -0700 (PDT) Received: from ?192.168.1.75? ( [86.144.172.37]) by mx.google.com with ESMTPS id f13sm15154064gvd.2.2008.06.18.15.19.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 18 Jun 2008 15:19:34 -0700 (PDT) Message-Id: <7FC243B1-B93F-4C45-9B61-844475F16FDD@gmail.com> From: Rob Davies To: users@activemq.apache.org In-Reply-To: <17992071.post@talk.nabble.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Subject: Re: It is possible to configure Broker/Client to use reliable-UDP-protocol for Topics and TCP/IP for Queues? Date: Wed, 18 Jun 2008 23:19:31 +0100 References: <17992071.post@talk.nabble.com> X-Mailer: Apple Mail (2.924) X-Virus-Checked: Checked by ClamAV on apache.org On 18 Jun 2008, at 22:16, Kosta wrote: > > It is possible to configure Broker/Client to use reliable-UDP- > protocol for > Topics and TCP/IP for Queues? > It is possible to configure Broker/Client to use UDP > multicast/multicast-protocol for Topics and TCP/IP for Queues? > > In other words could application create connection with different > underlying > protocol dedicated for Queues and Topics and force Broker to use > desired > protocol for different destination types including Temporary Queues > and > Topics? > > In addition it should be possible to configure in such way that all > synchronous requests from client(create connection, consumer, ect) > should > use reliable TCP/IP(as default) and only Publishing and Consume of the > messages should be done via UDP or reliable UDP or multicast. > > > BTW, what is the state of reliable-UDP-protocol? > We need a working reliable layer on top of UDP which is capable of > handling > re-requests of missing packets etc. and able to push Messages to all > subscribers at once but not via TCP/IP (Point to Point). Tibco like > and > hardware based messaging solutions. > > -- > View this message in context: http://www.nabble.com/It-is-possible-to-configure-Broker-Client-to-use-reliable-UDP-protocol-for-Topics-and-TCP-IP-for-Queues--tp17992071p17992071.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > Hey Kosta, currently ActiveMQ supports publish/subscribe using tcp - we do intend to offer a reliable multicast version later this year. However - this is a community project, and as such we encourage participation, so if there is something that you or your company needs that isn't there - please roll-up your sleeves and help! ;) cheers, Rob http://open.iona.com/products/enterprise-activemq http://rajdavies.blogspot.com/