KConfig race condition?

[Rob Kaper]

On Mon, Apr 19, 2004 at 10:24:19PM +0200, Waldo Bastian wrote:
> > I'm having a problem where two applications want to update KConfig at the
> > same time. Both application instances receive a notification to store a key
> > (a cookie*), but it has happened where the save of the second application
> > undid the change by the first. 
> 
> You need to do proper file-locking then. I can add a lock function to KConfig 
> for that if you like. (KDE 3.3)

Yes, please. I'd rather see the library (optionally) take care of that than
the application.

The applications needn't know about each other's new options yet, so signals
on file alteration aren't necessary fortunately, but I suppose KPilot might
like that? I've seen it work for the bookmark editor and Konqueror, at
least.

Rob
-- 
Rob Kaper     | 4/16 Horrorpops COPENHAGEN, 4/29 The Rasmus LONDON
cap at capsi.com | 5/11 Ghost of the Robot AMSTERDAM, 5/14 Disney PARIS
www.capsi.com | 7/19 COPENHAGEN-MALMÖ, 7/21 STOCKHOLM-KÖPING, 8/1 OSLO
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040419/d8f22eec/attachment.sig>