Another possible solution: It is possible to trigger a dummy SyncML session and get the DevInfo from the phone. The 'Man' and 'Mod' fields provides precise for us to find the real template correctly (and abort the dummy session silently).
We already need to work on this for HTTP based clients, I think it is possible to also make it work for Obex based phones. The only premise the phone responds with our SAN in the default dummy session. I think it is possible. See discussions in http://bugzilla.moblin.org/show_bug.cgi?id=7838#c8 Jussi Kukkonen wrote: >Jussi Kukkonen wrote: >> First, I was actually under the belief that SDP included vendor/device >> IDs but that doesn't seem to be the case. There are still some ways to >> do matching: >> 1) Syncml devices should responds to SDP service search for "SYNCML" >> 2) default device names are very commonly of type "Nokia N85" >> 3) Bluetooth addresses can be used to guess the vendor (IEEE OUI >> database) > >Congwu found the vendor/device ids, they are in "Device ID" profile. >Updated list: > > 1) Syncml devices should responds to SDP service search for "SYNCML" > 2) Some devices implement the Device ID profile with vendor/product > ids > 3) default device names are very commonly of type "Nokia N85" > 4) Bluetooth addresses can be used to guess the vendor (IEEE OUI > database) > >Testing at home, none of my devices seem to support Device ID though. >Looking a the device ID database would probably make it easier to >estimate if it's supported by the devices we are interested in but a >quick search didn't take me anywhere. > >> None of these is guaranteed to work so they should only be used as >> enhancements. > >This still applies. > > -Jussi Best Regards, Congwu _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
