KSyCoca, Thread safety, and Cache invalidation
sebas at kde.org
Sat Jun 13 03:04:31 BST 2015
On Saturday, June 13, 2015 02:04:03 Vishesh Handa wrote:
> 3. The gui thread on receiving the dbus signal updates its db as well
> as the database of all other threads. This is slightly complex and
> would require locking code similar to (2) since the other threads
> could be in the process of using KSycoca.
> I'm not quite sure on how to go about this. Do you have any
> suggestions? I'm leaning towards (3), but the locking code is scary.
7. the gui thread listens to dbus and sends a signal to the other threads?
Sebastian Kügler | http://vizZzion.org | http://kde.org
More information about the kde-core-devel