I think a seperation of layers would be advisable, but in a more abstract fashion than "core" and "bridge" - how about Toolset, Services, Application and Package (such as CMS - which is functionality consisting of multiple applications and services).
Obviously, the more generic stuff filters it's way to the bottom of the layered structure, whilst the more specific stuff filters it's way up. There are also dependencies and these should be identified, otherwise you run the risk of generic code being done at an application or package level, whilst the toolset does not grow - which means that many developers are repeating the same generic tasks, whereas they could be built once in the toolset which everybody will benefit from them. Regards Emile _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
