Even, if it is a core builder, it's better to implement the functionality where the responsibility should be. i.e. The syncnodes builder should be responsible for keeping the syncnodes up to date. Implementing it in MMObjectBuilder creates dependencies that are not needed, and e.g. disables you to use a 'MMBase lite' core that does not use syncnodes.I think 'syncnodes' is considered a 'core' builder, which you cannot not have. Obviously removing them is implemented in mmobjectbuilder itself because that is easier.
It's not a big deal, but it's nice to follow a clean OO design.
Rob
