http://bugzilla.moblin.org/show_bug.cgi?id=7089
--- Comment #27 from Chen Congwu <[email protected]> 2010-01-06 01:15:29 PST --- Another problem: how does this work smoothly for SyncEvolution based peers? In this case the device name from Bluez is meaningless, since Obexd SyncEvolution plug-in registered the SyncMLClient service with a special service name "Obex server for SyncML, using SyncEvolution", maybe we can get this information via Bluez dbus apis and detect it is a SyncEvolution peer? -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
