On Thu, 2007-12-27 at 16:13 +0000, Mark Ellis wrote:
> On Thu, 2007-12-27 at 13:51 +0000, John Carr wrote:
> >
> > Agreed. D-bus activation would be one way to achieve that - when the
> > sync plugin attempts to talk to sync-engine over dbus, sync-engine is
> > started by the dbus session daemon (therefore under the correct user
> > session). But i'm not sure how that would hurt sync-engine (hence my
> > original e-mail) - i suspect it wouldn't cope with it as the device
> > will likely try to sync in the background and the AirSync server just
> > won't have been started..
> >
>
> Ah ok, my lack of sync knowledge is showing here. I had assumed the
> device wouldn't try to sync until signalled from the host side, ie
> sync-engine, in which case we would have all the time in the world to
> start up whatever is required. I take it this is not the case.
>
The device won't sync until the partnership is set up and the RAPI
sync-resume command issued (i.e. sync-engine has initialized). So we
should be OK waiting.
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
