On Sat, 2007-12-22 at 13:29 +0000, Dr J A Gow wrote: > I have been investigating whether we can build legacy support into > sync-engine. It looks very much like this can be done.
Great! > The stumbling block is the fact that a legacy *dccm does not emit the > required d-bus messages to allow sync-engine to know it is there! I > tried vdccm with my old iPAQ h3800 series and PocketPC 2002. > > Now I confess not to have been following the various *dccm discussions > in detail so I am not fully up to date on the current thinking regarding > *dccm, but is there any likelihood of convergence with the various > *dccms towards a single one supporting both current and legacy devices - > or at least having them emit the same messages on connection? Mark implemented pre-WM5 support in odccm a little while ago[1]. Not having a pre-WM5 device, I have never tested it, but I do believe it works. This obviously means that you need not target any other dccm -- just concentrate on odccm. > Basically, in sync-engine, I would like to either call an API in or > have a d-bus message sent from the *dccm (preferably the latter) to > determine both the presence of a device and the device type, and thereby > know whether to use the legacy support or Airsync. Sounds superb! Hope this is helpful. [1] http://synce.svn.sf.net/viewvc/synce?view=rev&revision=2977 -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- 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
