Fwd: User bus conclusion

Oswald Buddenhagen ossi at kde.org
Wed Nov 10 08:29:39 GMT 2010

On Wed, Nov 10, 2010 at 09:10:48AM +0100, Thiago Macieira wrote:
> For example: KConfig has lock files so saving one file won't step on
> another instance's toes. However, does it really work? If the contents
> of the config file are read into memory and saved from memory, what
> happens to changes made to the file in-between?
it reloads the file and merges - in case of conflict the last flush wins
on a key-by-key basis.

> Same thing about kwallet: when saving a new password, does it really
> read in all of the old contents? Or does it try to save from memory,
> from when the wallet was opened?
dunno. it could certainly adopt kconfig's scheme.

> More importantly: if this is a use-case that we support, is there anyone 
> thinking of cases like the above and fixing them?
well, i'm sure most people are blissfully oblivious of the implications,
but that can be fixed on a case-by-case basis in the applications.

More information about the kde-core-devel mailing list