Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 55126 invoked from network); 29 Jan 2001 14:00:35 -0000 Received: from fw.infoplanning.net (HELO infoplanning.com) (@209.8.58.131) by h31.sny.collab.net with SMTP; 29 Jan 2001 14:00:35 -0000 Received: (qmail 16614 invoked from network); 29 Jan 2001 14:11:39 -0000 Received: from unknown (HELO apache.org) (192.168.0.189) by inet with SMTP; 29 Jan 2001 14:11:39 -0000 Message-ID: <3A7576AD.D51B88F6@apache.org> Date: Mon, 29 Jan 2001 08:57:01 -0500 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [C2][feature request][Datasource components] get-by-name +no-pooling References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Donald Ball wrote: > > On Sun, 28 Jan 2001, Berin Loritsch wrote: > > > a minimum amount of connections. The maximum is a hard maximum, and > > the getConnection() would fail if an additional one was needed--I need > > to look at waiting for one to free up though. The minimum is a soft > > minimum meaning that at least the minimum number of connections will > > be held in reserve unless we would have more than the hard maximum. > > that oughtn't be terribly difficult, but i'd like it to be configurable. > sometimes i'd want it to fail, sometimes i'd want it to wait (for a > certain of time, anyway). I was thinking about adding a timeout parameter to the pool-controller element. If the timeout passes before a connection is returned, then you have a failure. It would be configurable--and 0 (the default) would mean a hard failure without waiting.