Hi guys, After our meeting sunday, I was rethinking about the configuration interface and I remembered that I began to create objects that represent our configuration : for exemple task, datasources, ... but also enumeration which contains the different values which are useful for defining . I think that if we are interested in providing a configuration interface, every framework will present objects that contain the configuration logic. Before that anyone spend more time arround it, it could interesting to be have answers about these questions : - do you think it is a good idea ? - are these objects part of the lsc-core ? - if yes, do you have an idea of how to handle configuration versions and backward compatibility ? - if we use enumeration to declare the different data source for example, how to add customed sources to such fixed enumeration ?
Regards, -- Sebastien Bahloul M : [email protected] W : http://seb.homelinux.org/ _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
