----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/106318/#review18487 -----------------------------------------------------------
libnepomukcore/resource/resourcemanager.cpp <http://git.reviewboard.kde.org/r/106318/#comment14595> FYI, this required me to not initialize the ResourceManger on construction. This is not a problem since it gets initialized when anyone asks for the main model. - Vishesh Handa On Sept. 4, 2012, 7:21 a.m., Vishesh Handa wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/106318/ > ----------------------------------------------------------- > > (Updated Sept. 4, 2012, 7:21 a.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 > ----- > > libnepomukcore/resource/resourcemanager.cpp 198ad86 > services/storage/nepomukcore.cpp 56d079a > > Diff: http://git.reviewboard.kde.org/r/106318/diff/ > > > Testing > ------- > > > Thanks, > > Vishesh Handa > >
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
