Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 40227 invoked from network); 9 Nov 2000 02:46:57 -0000 Received: from chili.symmetrix.ch (212.55.206.33) by locus.apache.org with SMTP; 9 Nov 2000 02:46:57 -0000 Received: from symmetrix.ch (pepper.aps.ch [212.55.207.129]) by chili.symmetrix.ch (8.9.2/8.9.2) with ESMTP id DAA26200 for ; Thu, 9 Nov 2000 03:48:41 +0100 X-Envelope-To: � Message-ID: <3A0A102A.61F70A44@symmetrix.ch> Date: Thu, 09 Nov 2000 03:47:06 +0100 From: Herbert Hotz Organization: Symmetrix AG, Switzerland X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Re: draft final version of the esql namespace References: Content-Type: multipart/alternative; boundary="------------CEC509E8341608BE235B118F" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N --------------CEC509E8341608BE235B118F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Donald Ball wrote: > On Wed, 8 Nov 2000, Ulrich Mayring wrote: > > > Donald Ball wrote: > > > > > > if you're configuring the connection parameters dynamically, you shouldn't > > > be trying to use connection pooling imho. > > > > Ok and why not? > > mainly, it just doesn't make sense to me, to pool something that's > dynamic. however, i'll play along for the moment and ask you the same > questions i asked in another post. what data would an xsp page have to > provide to create a new connection pool, and what data would an xsp page > have to provide to check out a connection from that pool? > > i think it's possible to work something out here, though it may not be in > the scope of the esql namespace per se - the pool maintenance namespace > could be completely distinct. but we'll see. > > - donald > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org > For additional commands, e-mail: cocoon-users-help@xml.apache.org Hello esql folks, As a provider we host many websites from different customers. We want to offer also appliction services to our customers. So it seems very natural, that a customer wants to use 'his' databases - even if they are used by a common (Cocconn :-) application running on one of our own servers. Conclusion: We certainly want to have the possibility to dynamically assign connection pools. We don't like to have dirver, user, passwort, a.s.o. hardcoded in the xml pages and even worse in the generated java sources. If I imagine, that I have first to generate an xml file by some means, just to make things dynamic, than pipe that xml file through cocoon, which is compiling the generated source, to finally get the required database connectivity - I do not feel too comfortable. So, design esql that way, that it's tomorrow use will not be limited. Thanks for listening & kind regards Herbert -- +----------------------+-------------------------------------------+ | Herbert Hotz | Voice: +41 1 381 8880 | | Symmetrix AG | Fax: +41 1 381 2127 | | Muehle Tiefenbrunnen | GSM-SMS: +41 79 402 5704 | | Seefeldstrasse 231 | URL: http://www.symmetrix.ch/ | | CH-8008 Zurich | E-Mail: mailto:herbert.hotz@symmetrix.ch | +----------------------+-------------------------------------------+ --------------CEC509E8341608BE235B118F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Donald Ball wrote:

On Wed, 8 Nov 2000, Ulrich Mayring wrote:
> Donald Ball wrote:
> >
> > if you're configuring the connection parameters dynamically, you shouldn't
> > be trying to use connection pooling imho.
>
> Ok and why not?
mainly, it just doesn't make sense to me, to pool something that's
dynamic. however, i'll play along for the moment and ask you the same
questions i asked in another post. what data would an xsp page have to
provide to create a new connection pool, and what data would an xsp page
have to provide to check out a connection from that pool?
i think it's possible to work something out here, though it may not be in
the scope of the esql namespace per se - the pool maintenance namespace
could be completely distinct. but we'll see.
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org

Hello esql folks,

As a provider we host many websites from different customers. We want
to offer also appliction services to our customers. So it seems very
natural, that a customer wants to use 'his' databases - even if they
are used by a common (Cocconn :-) application running on one of our
own servers.

Conclusion:
We certainly want to have the possibility to dynamically assign
connection pools. We don't like to have dirver, user, passwort, a.s.o.
hardcoded in the xml pages and even worse in the generated java sources.

If I imagine, that I have first to generate an xml file by some means,
just to make things dynamic, than pipe that xml file through cocoon,
which is compiling the generated source, to finally get the required
database connectivity - I do not feel too comfortable.

So, design esql that way, that it's tomorrow use will not be limited.