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

List:       kde-devel
Subject:    Is KSharedConfig thread-safe ??
From:       "dukju ahn" <dukjuahn () gmail ! com>
Date:       2007-05-28 13:02:12
Message-ID: 9119cdb30705280602h4e87fc83mbf79a38f3be03fe0 () mail ! gmail ! com
[Download RAW message or body]

I expect that I sholud read KConfig configurations
from certain method, which is excuted by separate threadweaver.
The method is used to parse project files, and uses separate
thread to not block GUI.

Question is whether KSharedConfig is thread-safe or not.
The techbase tutorial says that

It thus provides a way to reference the same configuration object
from multiple places in your application without the extra overhead
of separate objects or concerns about syncronizing writes to disk
even if the configuration object is updated from multiple code paths.

But I'm not sure whether the above paragraph means thread-safety
or not. Or is it ok just to read from KConfig, not writing?
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]