Mika Raento wrote:
Do you refer to the DevInf document being a single CDDATA element ? I actually believe that is what libwbxml already does. However I never noticed it because the wbxml2xml tool hides this fact and simply displays the DevInf as normal elements in the node. I checked with a hex-editor and DevInf is indeed a CDDATA element. But now that you mentioned it , I had a look at the 3650 request document and whats indeed different between the request DevInf from the Nokia and multisyncs response is that the DevInf from multisync(libwbxml) is not a valid XML document. At least the doctype is missing. So, well thats kinda good to know. I'll be working on it this weekend ...I've been looking at the same thing (using a 7650, but the sw is the same) and I've found out the probable cause: The Nokia phones want the whole DevInf part encoded as a separate, opaque document in wbxml.
So I guess libwbxml should be modified so that it when seeing a DevInf
node:
- takes the whole DevInf element
- turns it into a document, complete with doctype
- encodes it as a separate wbxml doc
- adds the result as a opaque string to the parent
Bjoern
This is at least how the phone itselfs encodes the message, and it can definitely parse messages encoded like this (e.g. from the Calmeno sync server).
I don't have the time to do this at the moment, but if nobody else does
it I might be able to look into it in a couple of weeks time.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
