|
From: Michael B. <mic...@cm...> - 2008-01-08 11:00:00
|
Daniel Gollub schrieb: > Arg, yes - that could be as well.. since the latest syncml-obex-client might > already send it's own capailities in advance. SyncML Spec says that the > device then only should reply supported capabilities by the device... Why should this happen? > Not quite sure if syncml-obex-client is already sending the (own) entire > capabilities in advance or not.. it's up to your version of libsyncml. > Michael Bell that recently lots of development in this area ... we need have > to introduce finally same proper discovery function for syncml-obex-client > tool (and OpenSync plugin). Not quite sure how hard this is to implement. The syncml-obex-client is in fact a SyncML server according to the protocol. The name is a little bit misleading. I can only test the http stuff and here always the SyncML client sends the first DevInf. I use SyncML over http over bluetooth and sniff it with wireshark. If you do this with OBEX instead of http then you should see which sends the first devinf. Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin _______________________________________________________________ X.509 CA Certificates / Wurzelzertifikate http://ra.pki.hu-berlin.de |