Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6DF514C30 for ; Sat, 21 May 2011 03:30:52 +0000 (UTC) Received: (qmail 10907 invoked by uid 500); 21 May 2011 03:30:52 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 10863 invoked by uid 500); 21 May 2011 03:30:51 -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 10855 invoked by uid 99); 21 May 2011 03:30:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 03:30:49 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of slickqt@gmail.com designates 209.85.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-iw0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 03:30:44 +0000 Received: by iwn3 with SMTP id 3so4312287iwn.15 for ; Fri, 20 May 2011 20:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=8KTV6pTqgmC7NpF53VN1zYbAdjM6ei9YCNUWMHOOu1c=; b=sezFfL6VoaCuVKMI98/jN2bY8jp1LZLdFfx9qFRA8tWX8igo4L7zwH2NLVP9ekaLrB rm83i7NWqOCdmQrmkgwTTxImmMwyiqi99AQUzEmbJpC73VRWIe3Ujc4wrVG3GbWjtHd1 C56WqEcyX7aaS8CfYaZtVYq9q1jX/rwprIrmk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=goGj8iwnSStBPKU4k99pRuoorLvZf4lr4Upc2kOk9ZvHC2aVKZe9olx9WrUMs2q5i5 yp5wOmntrTkJiAzoVZ2GKLvTa/AakybZXsRuRdLQK/56UYZEDnq+y/aZAIT6fT1K9h15 3bMsAlH4Dt8bQbK9sgMJDSZfKT23HTikhsYAM= MIME-Version: 1.0 Received: by 10.42.97.5 with SMTP id l5mr5405685icn.504.1305948623374; Fri, 20 May 2011 20:30:23 -0700 (PDT) Received: by 10.43.47.134 with HTTP; Fri, 20 May 2011 20:30:23 -0700 (PDT) In-Reply-To: <3BDCA27C04F645509B91E10B1DE1531E@hope> References: <3BDCA27C04F645509B91E10B1DE1531E@hope> Date: Sat, 21 May 2011 11:30:23 +0800 Message-ID: Subject: Re: how to bind exchange to exchange like bind exchange to queue in the same broker? From: jun yang To: users@qpid.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable like a organization A has department A1,A2,A1 has sub department A1-1,A1-2, when mesage with subject A1-1 send to A, i want to A1 and A1-1 subscribers can receive such a message. any anoter solution to achive that? 2011/5/20 Steve Huston : >> for example: topic exchange ex-A,ex-A2,ex-A3, i want to bind >> ex-A->ex-A2(binding-key=3D'A2'), ex-A->ex-A3('binding-key=3D'A3'), is th= is >> possible? > > No, not as you've described. What are you trying to accomplish? > > -Steve > > -- > Steve Huston, Riverace Corporation > Total Lifecycle Support for Your Networked Applications > http://www.riverace.com > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: =A0 =A0 =A0http://qpid.apache.org > Use/Interact: mailto:users-subscribe@qpid.apache.org > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org