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 624DAD05A for ; Tue, 18 Dec 2012 03:10:05 +0000 (UTC) Received: (qmail 51105 invoked by uid 500); 18 Dec 2012 03:10:05 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 50490 invoked by uid 500); 18 Dec 2012 03:09:54 -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 50397 invoked by uid 99); 18 Dec 2012 03:09:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 03:09:49 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lanced@gmail.com designates 209.85.220.172 as permitted sender) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 03:09:42 +0000 Received: by mail-vc0-f172.google.com with SMTP id fw7so198435vcb.3 for ; Mon, 17 Dec 2012 19:09:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=/ILHqHKUU3Csr7Yw8JIR+YK1ZCvv0pczET34rqN45KM=; b=BKxJEFNKbQ/xk1iH9SqafNSvIYCLu5c5RPQSepzftcFAwcGqErHUF2Q/iYzN1/ubRC pXEiweztEHap5W9zZy0lc8UuKWuKbzNLi/DJdGORtvghReIdM7vf17wwNvqAkUs1LmsU dDyZi5LlUjePcatFYzR5MUs3DkRCWvTiaH36Uw8nUAwpDPcBDyI5YRELSyvp9dT/1mxr I6X7bqclKK2C0dHp/appI7aVpq5piJW2zx61ydQ0euje/uY/dKzn1ERYzSRBr0ScYE+2 Z12YXdLmrpUvwz4PZzNyARSsPhkDu3WkJ44dHtt7akqKNSClLQLAzAB50vFkV3E2hLAS MgSA== Received: by 10.220.157.9 with SMTP id z9mr747601vcw.45.1355800160990; Mon, 17 Dec 2012 19:09:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.220.106.206 with HTTP; Mon, 17 Dec 2012 19:09:00 -0800 (PST) From: "Lance D." Date: Mon, 17 Dec 2012 22:09:00 -0500 Message-ID: Subject: limit policy on bound temporary queues To: users@qpid.apache.org Content-Type: multipart/alternative; boundary=f46d043bdffafb764c04d117d2d7 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bdffafb764c04d117d2d7 Content-Type: text/plain; charset=ISO-8859-1 Hello, I'm trying to figure out a problem and I'm hoping to find the right way to make this happen. I've got a data producer that publishes to an fanout exchange. My system requires that under no circumstances can the producer get throttled because even if 1 user can't keep up, the other consumers need the data as soon as possible. My thought is that if I just force all of the consumers to connect with a 'ring' limit policy, then I should be okay because slow consumers will just drop data on the floor. So I'd like to be able to make that the default policy. That said, I'm fairly certain that isn't possible, so I'd at least like to setup my clients with the correct settings. I've read through the documentation, but I can't seem to figure out how to register to receive from an exchange, using a temporary (implicit) queue. Thanks in advance for the help. -Lance --f46d043bdffafb764c04d117d2d7--