On Fri, 2012-03-16 at 13:54 +0100, Krzesimir Nowak wrote: > 2012/3/16 Patrick Ohly <[email protected]>: > > On Thu, 2012-03-15 at 14:43 +0100, Patrick Ohly wrote: > >> I still think resources should be added to m_waitingResources before > >> construction is complete. Activating the object and notifying the > >> caller > >> can wait until the resource is really usable (= helper ready). > > > > And one more observation: running the helper should get delayed until it > > is really needed, which probably means until the resource is ready to > > become active. > > Not really, I am afraid - there are methods that does not need Session > to be active. GetStatus for example. Or maybe I did not understand > you.
Who says that GetStatus() has to be implemented in the helper? ;-) Putting its implementation into the syncevo-dbus-server would allow delaying the helper startup and make the server/helper API smaller. A downside might be that the server replies with slightly stale data, but that's not a bug. It'll correct itself as soon as the server gets the next status update from the helper, which then triggers a statusChanged signal in the server. This is the same question that I just raised for connection: where do we put which part of the implementation? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
