D22339: Make sure solid backends are reentrant

[Stefan Brüns]

bruns added a comment.


  In D22339#494149 <https://phabricator.kde.org/D22339#494149>, @apol wrote:
  
  > In D22339#494142 <https://phabricator.kde.org/D22339#494142>, @bruns wrote:
  >
  > > How do you guarantee *each thread local* copy now is connected to the right signals, i.e. the socket notifier for the mtab and inotify for fstab?
  >
  >
  > each backend will create things separately now, so it should work like it used to so far when there was just one thread involved.
  
  
  The invalidation has to be done per thread then as well, which you don't do. See fstabmanager.cpp

REPOSITORY
  R245 Solid

REVISION DETAIL
  https://phabricator.kde.org/D22339

To: apol, #frameworks, davidedmundson, bruns
Cc: bruns, kde-frameworks-devel, LeGast00n, michaelh, ngraham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20190711/a8fac10b/attachment-0001.html>