On Thu, Jul 13, 2006 at 09:48:00PM +0200, Yannick Lecaillez wrote: > So, the other possibility, wich is imho, less disappointing than using an > old-school configuration file is to use a great library like libelektra ;-)
My personal taste would be to configurer elektra with a backend that understand old-school configuration file like ini files ;-). Seems like this backend is on the way... > The idea is to map specific keys to specific backends. > > The default, hardcoded behaviour is to map system/, system/elektra & user/ > to the filesys backend. Providing filesys as default backend. I find your plan rather appealing, except that the default mapping should be a compile time choice. That wouldn't be hard, and a longer term goal. Having the filesys backend as default backend seems right to me to begin with. > That's just an idea for bring flexibility about backend while keeping > the stuff as simple as possible. So thanks to comment & react ;-) Something along those lines seems to be required in order to be able to use more than one backend at one time. Seeing the elektra information as a tree one could design a 'language' able to specify as best as possible a partition of the tree and assigne property to each of the elements of the partition. Does such a language allready exist? It could be used to map each part of the tree to a backend. It may also be too complicated and overkill, in that case what you proposed (specify partition by the top node of a sub-tree) seems right. -- Pat ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Registry-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/registry-list
