Dr J A Gow
2007-12-22 13:29:58 UTC
Folks,
I have been investigating whether we can build legacy support into
sync-engine. It looks very much like this can be done.
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?
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.
John.
I have been investigating whether we can build legacy support into
sync-engine. It looks very much like this can be done.
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?
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.
John.