The Palm client (from http://www.synthesis.ch) uses WBXML, it's connecting to the server across a PPP link over Bluetooth which is routed through my PC's net connection. I do quite a lot of work with XML so I know about the CDATA encapsulating data you don't want parsed - I am just unsure as to where the CDATA should be removed - at the client or the server end... just for reference, I'm using the Sync4j server (http://sync4j.sourceforge.net)
What is happening with the palm client is the following: sync starts palm sends data about changes (in WBXML) to server Server un-WBXMLs it, and acts on it, constructs responses and sends them back in WBXML The response from the server includes <Add> events for the entries added by Multisync, e.g. <Add><CmdID>2</CmdID> <Meta><Type xmlns='syncml:metinf'>text/clear</Type></Meta> <Item> <Source> <LocURI>pas-id-3F4B790300000000</LocURI> </Source> <Data><![CDATA[BEGIN:VCARD VERSION:2.1 X-EVOLUTION-FILE-AS:Ximian, Inc. N: LABEL;WORK;ENCODING=QUOTED-PRINTABLE:401 Park Drive 3 West=0ABoston, MA 02215=0AUSA TEL;WORK;VOICE:(617) 236-0442 TEL;WORK;FAX:(617) 236-8630 EMAIL;INTERNET:[EMAIL PROTECTED] URL:www.ximian.com/ ORG:Ximian, Inc. NOTE:Welcome to the Ximian Addressbook. UID:pas-id-3F4B790300000000 END:VCARD ]]></Data> </Item> </Add> These type of entries are not recognized properly by the Palm client, which returns a 415 (Unsupported media type or format) status for each of them: <Status> <CmdID>3</CmdID> <MsgRef>2</MsgRef> <CmdRef>2</CmdRef> <Cmd>Add</Cmd> <SourceRef>pas-id-3F4B790300000000</SourceRef> <Data>415</Data> </Status> The Palm entries are sent as Type=text/x-vcard entries: <Replace> <CmdID>31</CmdID> <Meta><Type xmlns='syncml:metinf'>text/x-vcard</Type></Meta> <Item> <Source> <LocURI>10711152</LocURI> </Source> <Data>BEGIN:VCARD VERSION:2.1 N:New;Contact;;; TITLE: ORG:; TEL;WORK;PREF:125 EMAIL:[EMAIL PROTECTED] ADR:;;;;;; NOTE: END:VCARD </Data> </Item> </Replace> So I guess I have a second question, which is: which is right? The Palm client or Multisync? Should vCard data be sent as Type=text/x-vcard by Multisync? Or should the Palm client accept text/clear entries, and then check if the payload is a vCard? On Fri, 2003-12-12 at 08:04, Gideon N. Guillen wrote: > Well, if your Palm's SyncML client should handle the CDATA tags > correctly, otherwise, your SyncML client has a broken XML parser because > it's part of the XML standard. :) CDATA sections are there to tell the > parser not to parse any data in CDATA sections. This is needed if for > example there might be data, tags, elements, whatever that you don't > want the parser to parse because it would mess up things. An example of > this is you happen to include another XML document within another XML > document but you don't want the parser to parse this, just store it as > is. > > Now, if you're Palm's SyncML client is using WBXML (which I suspect that > it's using considering the bandwidth you have on most Palms stuck with > IrDA and RS232/USB connections), then CDATA tags are completely > irrelevant because there are other ways to indicate this in WBXML. > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Multisync-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/multisync-users ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Multisync-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-users
