KIOAccessManagerFactory and QtQuick2

[David Faure]

On Wednesday 14 May 2014 20:06:17 Albert Astals Cid wrote:
> El Dimecres, 14 de maig de 2014, a les 12:09:54, Marco Martin va escriure:
> > On Tuesday 13 May 2014 18:31:06 Aleix Pol wrote:
> > > Hi,
> > > I've been getting some error messages [1] from some QML applications and
> > > I
> > > decided to investigate a bit further. I realized then that most of it
> > > was
> > > coming from the KIOAccessManagerFactory that is automagically being set
> > > up
> > > by KDeclarative::setupBindings.
> > > 
> > > I've been trying it commenting out the NetworkAccess set and it seems to
> > > work well. I suggest we shouldn't force KIO NetworkAccess usage until it
> > > behaves properly from different threads (if that can ever happen).
> > > 
> > > Thoughts?
> > 
> > looks like we have to disable it for now, yeah
> > (some things will always need, like folderview tough)
> > 
> > any idea if kio may ever become thread safe?
> 
> Why do you need KIO to be thread safe if kio is non blocking and executes
> all the heavy stuff in different processes?

Because it used various singletons in the library (unprotected, i.e. with data 
races), before getting to the point of executing the stuff in different 
processes :-)

This is fixed now (mostly).

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5