<Eduard Witteveen:> > IMHO turning builders to inactive is not very wise. Please do not use > this. It can also lead to a lot of other problems...
Like what? I can think of two good reasons to turn off builders: 1) To have multiple MMBase instances running, using the same cloud. It's not necessarily desirable to have the same set of builders active on all instances.For example we're running a configuration in which one instance has read-only access to the database. The "mmservers" builder has to be inactive here, to prevent it from updating its table at regular intervals. 2) To deactivate legacy builders. If you can add items to a system, you should also be able to remove it gracefully.Even a standard MMBase configuration, installed out of the box, activates builders that I don't need. I'd like to hear what kind of problems can arise from inactive builders. Rob van Maris Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 -------------------------------------------------------------
