[Javtools-poolmngr] Requirements

[Amit D. <ami...@ra...>]

Hi All ,
         This mail is to initiate the design phase of the Pool Manager.
Before we move on the the architecture or the technical design , Stephen and
I thought we need to have the requirements listed first.
Stefaan you will need to edit this set of initial requirements this is a
very rough draft.
Others please feel free to contribute too.
Requirements
1.A PoolManager which could manage database pooling for 'n' databases.
2.Configuration of the Pool Manager needs to be in XML format.
3.Support for commit and rollback; user can handle this .Liken the situation
to setAutoCommit as false in jdbc, the user then has 
   control over the commit and rollback.
4.Support for isolation levels (this is database dependent but do give the
user to state an isolation level) if the underlying database   
   supports this isolation level.
5.A unused connection "sweeper", liken this to a garbase collector , unused
connections or timed out connections not returned to the 
   pool are regained.
6.Support for cached Prepared Statements.

   Also we could evaluate some existing pool managers (please do pass on the
links to such existing mangers) and list out the desired features.This could
lead us to a list of desired features missing in the existing pool managers
and help us build a better pool manager.
   I have used a pool Manager  www.protomatter.sourceforge.net .
   Need your opinion on the rqeuirements so that we can all agree and freeze
them.
   The next phase could be the technical architecture.
Regards,
Amit