[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] KConfigBackend
From:       ossi () mail ! kde ! org
Date:       2002-02-23 11:37:11
[Download RAW message or body]

> > * Adds setFileWriteMode(int) to create new files with a mode other
> > than 0600 which is the default.
> 
> This assumes that KConfig will be backed by a file.  What about an
> LDAP or other non file backend? 
> 
that's the ugly part. see my comment in the other thread.
but let's face it: kconfig is file-centric anyway. only kconfigbase
doesn't seem to be.

btw, kconfigbase is designed for "flat" files (only divided into
sections). hierarchical structures can be emulated by using the whole
path as a group specification. but then operations like "delete whole
branch" would have to process all groups beginning with the requested
pattern instead of "just" deleting the right node (which would dispose
it's children automatically) - all in all a hack. so basically it's
mostly purposeless to create an xml or ldap backend unless we change 
the whole design.

> This should probably go into the KINIConfigBackEnd class or
> whathaveyou.
>
yes, but somehow you have to "pipe" it to the backend.

greetings

[prev in list] [next in list] [prev in thread] [next in thread]