Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 84914 invoked from network); 5 Nov 2009 15:05:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Nov 2009 15:05:40 -0000 Received: (qmail 26141 invoked by uid 500); 5 Nov 2009 15:05:39 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 26109 invoked by uid 500); 5 Nov 2009 15:05:39 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 26063 invoked by uid 99); 5 Nov 2009 15:05:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 15:05:39 +0000 X-ASF-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tross@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 15:05:36 +0000 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id nA5F5ESD011084 for ; Thu, 5 Nov 2009 10:05:15 -0500 Received: from dhcp-100-18-254.bos.redhat.com (dhcp-100-18-254.bos.redhat.com [10.16.18.254]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id nA5F5E6A024146 for ; Thu, 5 Nov 2009 10:05:14 -0500 Message-ID: <4AF2E9AD.9080207@redhat.com> Date: Thu, 05 Nov 2009 10:05:17 -0500 From: Ted Ross User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: qpid-route References: <868635.67849.qm@web62103.mail.re1.yahoo.com> In-Reply-To: <868635.67849.qm@web62103.mail.re1.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 10.5.11.21 On 11/05/2009 09:02 AM, nicolae claudius wrote: > Hello, > > I use a custom (modified for custom LDAP authentication) qpid broker version 0.4 > I want to use federation between two brokers in Layer 3 network topology, by means of "qpid-route". > The problem is that this command is nowhere in my qpid-0.4 source tree, neither in installation files (make install). > > I belive that theese files are in qpid-python project, wich belongs to qpid 0.5 version. > Is it posible that i use that package to configure federation in my 0.4 broker. If not, what can I do? > > regards, > Nicolae Claudius > > PS. > The project needs an oficial IRC channel (mabe #qpid on freenode?) > > > > > Hi Nicolae, Using tools introduced in 0.5 to manage the M4 broker is probably not a good idea. I believe qpid-route was present in the M4 release (in qpid/tags/M4/RC9/qpid/python/commands/qpid-route) so I'm not sure why you don't see it. Did you branch a custom build because M4 didn't support your LDAP requirements? Is there a reason that the cyrus-sasl libraries (used by the broker to handle authentication) don't meet your needs for LDAP? In general, if you branch the project and make your own modifications, you either can't use new features and bug fixes introduced later in Qpid or you need to continually re-base your branch. -Ted --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org