[Nepomuk] Review Request: NepomukStorage: Start the different services in a separate thread

Vishesh Handa me at vhanda.in
Tue Sep 4 07:21:21 UTC 2012

This is an automatically generated e-mail. To reply, visit:

(Updated Sept. 4, 2012, 7:21 a.m.)

Review request for Nepomuk and Sebastian Trueg.


Use the ResourceManager::setOverrideMainModel instead


    Currently the QueryService internally uses the ResourceWatcher and the
    QueryParser, both of which use the Resource class. The Resource Class
    internally, requires the ResourceManager which uses the
    NepomukMainModel. This main model uses a local socket to connect to the
    storage service.
    Unfortunately, the soprano code is blocking and relies on a select call,
    so we cannot have both the server and client on the same thread, which
    is the case right now.

Diffs (updated)

  libnepomukcore/resource/resourcemanager.cpp 198ad86 
  services/storage/nepomukcore.cpp 56d079a 

Diff: http://git.reviewboard.kde.org/r/106318/diff/



Vishesh Handa

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20120904/4a7aca49/attachment.html>

More information about the Nepomuk mailing list