On Wed, 3 Nov 2004 15:38:14 -0500, Alan Cox <alan@xxxxxxxxxx> wrote: > On Wed, Nov 03, 2004 at 09:09:07PM +0100, D. Stolte wrote: > > gconf is not much better than the m$ registry imho. > > gconf has several advantages in its design like the ability to use > arbitary back ends (see the mbox demo for lunacy value) and good notifier > handling for dynamic change. It too had the one file per key design bug but > that has gone away Elektra also has key and keys change notification with kdbMonitorKey() and kdbMonitorKeys(), and can have multiple back ends. See http://elektra.sourceforge.net/elektra-api/html/group__kdb.html Elektra focus is on the API design and unified namespace. The one-file-per-key is a current implementation and makes single key writes way easyer to implement. It also leverages the hirarchical organization, and security model the filesystem already provides you. It has issues also, but as Michael said, it can be improved in the future without affecting applications source, etc.
