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

List:       kde-devel
Subject:    Re: Best technic to spread config changes?
From:       David Faure <faure () kde ! org>
Date:       2005-06-17 12:15:30
Message-ID: 200506171415.31312.faure () kde ! org
[Download RAW message or body]

On Friday 17 June 2005 12:45, Friedrich W. H. Kossebau wrote:
> Hm. How does this all relate to the system config cache? 
It doesn't, at all. The system config cache is about .desktop files, not kfoorc files.

> How costly is reparsing? 
It is somewhat costly of course, but it's the only way to pick up new stuff
from a config file. OK you could decide to always ship the data in the DCOP
call to avoid it... No risk of overwriting the data with older data btw, kconfig
does a reparse-before-save when needed.

> And there won't be any race conditions doing it the following way? 

> Config changing app CCA: 
> 1. save changed config
> 2. spread news about change
> 
> Starting app SA:
> A. register to DCOP
> B. read config

I don't see where a race could be. Either B is after 1, and the SA sees the new config,
or A is before 2, and SA gets notified properly.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]