Re: [Javtools-poolmngr] Suggested course of action

[Stefaan D. <st...@ya...>]

Hi,

I agree on the all of these requirements.
But I have some suggestions to make:
1) Would it not be better to encapsulate the connection object and provide a type
shell to execute statements.
2) On bases of the number 1 we could also provide a transaction mechanism. (Execute
several statements at ones).

3) Another possible solution is to implement the requirments as described by
Isabelle and later on provide a database shell (A easy to use class for the user to
request actions on the database).


Stefaan

--- Isabelle Muszynski <met...@pa...> wrote:
> Personally, I think that for the first release the requirements should be :
> 
> (1) provide pooled connections to users
> (2) the connections in one pool can be either all the same type of JDBC
> connection (same connection URL, username/password) or they can be different
> type. An other alternative would be to have more than one pool, and each
> pool is homogeneous.
> (3) the user protocol is : borrow, use, return.
> (4) we can set some policies as to how long a connection may be in use
> (difficult in real life, because a very busy servlet might hold on to the
> connection for a long time)
> (5) the pool is self-regulating : grows when connection demand is intensive,
> shrinks when less demand
> (6) configuration thru XML config file
> 
> IMO these are sufficient for a first release.
> 
> isabelle
> 
> ----- Original Message -----
> From: "Amit Deshpande" <ami...@ra...>
> To: "PoolManager (E-mail)" <Jav...@li...>
> Sent: Friday, August 02, 2002 8:24 AM
> Subject: [Javtools-poolmngr] Suggested course of action
> 
> 
> > Hi All,
> >          Suddenly there's a lull ...
> > anyway how about getting the requirements from a user point of view listed
> > first,
> > we already have a few requirements listed.
> > We could have a look ta some existing pool managers  and jot down some
> > features which are missing and are desired.
> > We could then freeze the requirements.Lets not mix the technical
> discussions
> > with these.
> >        As far as the technical discussions like server crash,chunking etc
> > are concerned lets get to tackle those after the requiremenst are
> over.These
> > are internal implenentations transparent from an end user point of view
> and
> > implemented to enhance performnace of the pool-manager.So we could after
> the
> > requirements phase list some critical issues like performance
> > enhancers,bottlenecks,configuration methods ,scalability mechanisms and
> > could have  a detailed discussio on those before proceeding to the design
> > phase.
> >      I need your comments on these, esp Isabelle.
> > - Amit
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Javtools-poolmngr mailing list
> > Jav...@li...
> > https://lists.sourceforge.net/lists/listinfo/javtools-poolmngr
> >
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Javtools-poolmngr mailing list
> Jav...@li...
> https://lists.sourceforge.net/lists/listinfo/javtools-poolmngr


=====
Stefaan Delanghe
ICQ: 110055343

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com