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

[Vishesh Handa]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/106318/#review18459
-----------------------------------------------------------


Another option that I thought of is to use ResourceManager::setOverideMainModel( .. ), that way we won't be connecting over the local socket.

- Vishesh Handa


On Sept. 3, 2012, 1:25 p.m., Vishesh Handa wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/106318/
> -----------------------------------------------------------
> 
> (Updated Sept. 3, 2012, 1:25 p.m.)
> 
> 
> Review request for Nepomuk and Sebastian Trueg.
> 
> 
> Description
> -------
> 
>     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
> -----
> 
>   services/storage/nepomukcore.h a3cfe6e 
>   services/storage/nepomukcore.cpp 56d079a 
> 
> Diff: http://git.reviewboard.kde.org/r/106318/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Vishesh Handa
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20120903/445cfdf2/attachment.html>