Nico Klasens <[EMAIL PROTECTED]> wrote: > The bridge should just be an entry point to the mmbase engine. The > outside world has to go through the bridge to interact with the engine. > The bridge will protect the engine for malicious use. The engine should > be responsible of managing the objects, builders, modules and other cool > stuff. The interfaces of the bridge do not cover all the functionality > and they should not. At least that is how I see it.
Yes, of course. But I would really like to see the 'core' to be more bridge-like. Now you have to learn a complete new, and not very friendly, language if you want to add e.g. new functionality to a builder (extending MMObjectBuilder), which is a rather normal thing to do. I'd very welcome a nicer way to do this, and one of the first things which would come in mind is a core implementing bridge (or core and bridge implementing the same sub-interfaces). Michiel -- Michiel Meeuwissen Mediapark C101 Hilversum +31 (0)35 6772979 nl_NL, eo, en_US mihxil' []()
