#2 Configuration file needed

[Anonymous]

Monaco would benefit from having it's configuration defined in a separate file, (as xml?) but not tied to any internal structures.

That is, values could be given in a normal xml node tree, but once the configuration is read into memory, the system could access the data by name.

Internally something similar to configuration.getValue("monaco.server.beacon.ip).

That way, the system structure could change radically, but any users of the system could still keep their old configuration files, even after upgrading.

Admitedly this could lead to some old names being completly out of synch with what is really going on, but this could be solved by intoducing "renaming" in the configuration file.

By adding this abstraction between what is given by the user and what the system is seeing internally, a change to either one does not need to propagate through every part of the system.