Peter Donald wrote:
>
> >> My actual suggestion would be to start with the XML Configuration
> >> component, along with the Testing Suite, supported by a site
> >> infrastructure designed to scale to multiple components.
> >
> >And to test that scalabilty, lets do DBConnection Pool as well :)
>
> I have a few concerns about this plan of attack. When we are building these
> components how will this evolve. I expect at the start that they will
> largely be independent. Then someone will need configuration data for DB
> pool and thus they will use the XML Config component to get it. This is
> integrated on top of that.
Sure. 'On top of' being the key phrase there. Hopefully the DBCP is
untouched, or at least the standard interfaces are untouched.
>
> Now a bit down the line it is decided that there needs to be a way to share
> connections and share components between DBPools and a native system (ie
> may need to do transaction monitoring etc) so someone decides to integrate
> DBPool into a service directory.
Ok. So I interpret this as they are *using* the DBCP still.
> Now this DBPool is part of a framework rather than an API - and depending
> on framework parts chosen (ie whos configuration component and whos service
> directory - turbine, avalon or struts) we have just built yet another
> framework.
The way I hope, it is *used* by a framework, not *part of* a framework.
Hopefully, down at the bottom, there is still a useful DBCP that stands
on it's own. I know there is no standard interface for a DBCP except
that they seem best when you don't know they are there : they look like
a Driver.
Maybe what this does is have the DBCP provide hooks to work with larger
scale entities. I dunno. I can't see that far. This sounds like stuff
someone already knows, or we will find out through doing. I would
prefer to see this shot down if 'someone knows'.
> We need to define clearly wear the difference between this project is and
> where Avalon is.
Sure. But it seems to me we just went full circle and are back to
considering Avalon as a framework again. Ohh, head hurts, head hurts :)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
