On Fri, 2003-12-12 at 08:12, Kevin James wrote:
> Thanks for that heads up.  I've changed it so that now Evolution syncs
> directly (through Multisync) with my SyncML server.  I'm still not
> getting changes synced back from the server to Evolution.  Not all bad
> news, as I think I've pinpointed the problem.
> 
> The other device that is syncing to my SyncML server is a Palm - that
> just writes the vCard data as each entry.  However, Multisync is
> writing each entry (from Evolution, in my case) wrapped in
> <![CDATA[]]> tags.  I assume that if Multisync expects to see these
> tags around the entry and discards (and doesn't send to Evolution) if
> they're not there.
> 
> My questions, therefore, are:
> Is my assumption correct? And if so,
> Should Multisync be doing this - or stripping the tags off before
> syncing data out?

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

Reply via email to