2005/9/16, Pierre van Rooden <[EMAIL PROTECTED]>: > Kees Jongenburger wrote: > > >We do that all the time(images,email,lucenes), so this is a non > >argument. as long as the core doesn't get to much deps it's fine by > >me. > > > The difference is that in your examples there are actually functional > reasons to have different implementations (i.e. convert is available on > your system or not), or they are applications you install seperately. I > would rather not want two implementations in the core that do the same > thing. > If people like to ship the whole of jakarta commons with mmbase, fine, > but don't go also implementing the stuff again. It seams you can now do 3 things -use the app server's data source (no new deps for mmbase) -use the legacy connection polling that implements a datasource (an optional module) -use an mmbase module that creates a datasource(an optional module)
so I don't see why we need to have this in the core since it's possible not use it _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
