On Thu, 2007-12-27 at 17:40 +0000, John Carr wrote:
> > 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.
>
> This is the bit i wasn't so sure about, particularly in the context of
> the triggerconnection program which was merged in to odccm. This is
> good to know, and adding dbus activation should be a simple as
> shipping a dbus .service file, along the lines of this:
>
> http://svn.gnome.org/svn/conduit/trunk/data/org.conduit.service.in
>
> Though i presume @bindir@ would be populated differently for a
> setup.py based installation. This fits in for jagow as well. In his
> case, sync-engine starts with his session so org.synce.whatever is
> available and dbus activation never has to do anything.
Is it worth my while popping some code in sync-engine to allow it to run
once and then terminate: i.e. run, allow a device to be connected, and
then when the device is disconnected shut down and exit. I could do this
either with a config.xml parameter or a command line switch - which
would be preferred?
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
