Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 5623 invoked from network); 22 Apr 2010 14:44:16 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Apr 2010 14:44:16 -0000 Received: (qmail 66195 invoked by uid 500); 22 Apr 2010 14:44:15 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 66173 invoked by uid 500); 22 Apr 2010 14:44:15 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 66165 invoked by uid 99); 22 Apr 2010 14:44:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 14:44:15 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Apr 2010 14:44:10 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1O4xd7-0008Av-LO for users@camel.apache.org; Thu, 22 Apr 2010 07:43:49 -0700 Message-ID: <28329877.post@talk.nabble.com> Date: Thu, 22 Apr 2010 07:43:49 -0700 (PDT) From: dnn To: users@camel.apache.org Subject: Re: Handle finite number of remote requests? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: Daniel.Nawrocki@ngc.com References: <28301621.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org That's pretty close to what I want to do, but the ThrottlingInflightRoutePolicy appears to throttle at the end of the route (or so it seems from the 'onExchangeDone' method). I think I could make it work by writing my own policy to check the DB in the 'onExchangeBegin' method. Thanks Claus! Claus Ibsen-2 wrote: > > Hi > > Something similar you can do is to throttle intaking messages > according to some metrics, such as the rate of speed > that external server can handle. > > Check out RoutePolicy > http://camel.apache.org/routepolicy.html > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://old.nabble.com/Handle-finite-number-of-remote-requests--tp28301621p28329877.html Sent from the Camel - Users mailing list archive at Nabble.com.