[apaku at gmx.de: Threadsafe access to a KConfig object]

Matt Rogers mattr at kde.org
Fri Jun 1 02:55:12 BST 2007


On Thursday 31 May 2007 19:14, Andreas Pakulat wrote:
> On 01.06.07 01:56:45, Thiago Macieira wrote:
> > Andreas Pakulat wrote:
> > >So we'd like to get some ideas as to how we can make the access to the
> > >project configuration threadsafe, without letting each plugin know what
> > >the config files are that are used to create the KConfig object (the
> > >setup code should stay internal to the project class).
> >
> > Protect it with a mutex or a RWLock.
>
> Right, I forgot to add that we're trying to find a way that doesn't
> involve having
>
> project->lockConfiguration();
> project->projectConfiguration();
> project->unlockConfiguration();
>
> each time we try to access the project configuration.
>
> Andreas

if that's what we have to do, that's what we have to do.
-- 
Matt




More information about the kde-core-devel mailing list