Re: CRLF in <string> -- XML vs XML-RPC
[email protected] 10 May 2007 01:04:58 +0000
| Newsgroups | gmane.text.xml.rpc.specification |
|---|---|
| Message-ID | <[email protected]> |
>> That's hard to believe. You mean the conventional PHP XML parser
>> doesn't normalize CR/LF ever? Considering 1) that the XML spec makes
>> it pretty clear that it's required; and 2) it's generally very useful,
>> I don't think it could get away with that. Plus, I have an Expat
>> parser from 2001 that has the normalization integrated pretty tightly
>> into it.
>Well, I quoted from memory, and I am most likely wrong. I just
>re-read the spec, and as you correctly pointed out in chapter 2.11 the
>normalization is in fact required upon parsing.
Well, there's still some confusion, because I have a user who, using
your implementation as a standard by which to measure mine, claims
that yours does _not_ do line ending normalization on the receiving
side (specifically, where a server receives a <string> parameter).
Could you have been wrong about the fact that you (PHP XML-RPC) use
the standard PHP XML parser but right about the fact that the PHP
XML-RPC server doesn't do line ending normalization?
Same user says a Python XML-RPC server does _not_ do line ending
normalization of <string> parameter values.
--
Bryan Henderson San Jose, California
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xml-rpc/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/xml-rpc/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[email protected]
mailto:[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/