Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 24064 invoked from network); 19 Jul 2006 06:50:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Jul 2006 06:50:54 -0000 Received: (qmail 96840 invoked by uid 500); 19 Jul 2006 06:50:53 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 96462 invoked by uid 500); 19 Jul 2006 06:50:52 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 96451 invoked by uid 99); 19 Jul 2006 06:50:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jul 2006 23:50:52 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com designates 64.233.182.190 as permitted sender) Received: from [64.233.182.190] (HELO nf-out-0910.google.com) (64.233.182.190) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Jul 2006 23:50:50 -0700 Received: by nf-out-0910.google.com with SMTP id x4so143531nfb for ; Tue, 18 Jul 2006 23:50:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=q49pDVueccRGxuMpspxXE0d6/bxG/2OhdwYvtVufEHW+m8fqPWTbuLjx8xIIW/6SRbAUiGFZE1zXAufzg+nVPUX6VCRXbqq3SYjJprAZY2pLl9nQCSuTzskU0W9CtZ+GQu2puOkWM0NyoYnY46BN1LUoD7QYaItO2qskZs65WRo= Received: by 10.78.185.7 with SMTP id i7mr163758huf; Tue, 18 Jul 2006 23:50:28 -0700 (PDT) Received: by 10.78.174.8 with HTTP; Tue, 18 Jul 2006 23:50:28 -0700 (PDT) Message-ID: Date: Wed, 19 Jul 2006 07:50:28 +0100 From: "James Strachan" To: general@incubator.apache.org Subject: Re: [Proposal] Blaze In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44BD318D.2080308@redhat.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 7/19/06, Noel J. Bergman wrote: > Totally unrelated ... JMS has the ability to create a message filter, but > one of the limitations is that the filter is applied when the receiver is > created, rather than when a get operation is executed. This makes sense for > the push receiver case, but is limiting for the pull receiver case. Does > AMQP have anything to say about this aspect of messaging, or does it stay > strictly in the messaging provider space, and away from the client API? Could you explain a little more about your use case - it sounds interesting :). Do you only want to fetch a single message with a different filter per message, or just change the fliter from time to time. If its the latter then creating JMS consumers is pretty cheap & you can use any JMS to do that. Though the former, there's no 'give me a message using filter X' type operation. FWIW it wouldn't be too hard to add this to blaze or activemq - its just a different kind of operation. Messaging systems are usually designed for asynchronous streaming of messages, so you subscribe and receive many messages etc. -- James ------- http://radio.weblogs.com/0112098/ --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org