> > > it might event be worse.. what about having the bridge in it's onw > > package so > > > > "somebody" can write an other mmbase bridge implementation? > > > I disagree. The bridge is in my opinion something that belongs to the > MMBase core. It defines a standard interface on which application can be > build. Creating different interfaces will make things less standardized > and more hard for people to make applications that work on 'all' MMBase > systems.
In fact you do agree <quote> It defines a standard interface on which application can be build. </quote> So the mmbase core "only" implementation of the interface. I am not thinking about changing the interface .. but more about the core. moost apps i build only require the bridge classes to compile
