note 87642 deleted from function.xmlrpc-encode by danbrown
| From: | danbrown@php.net | Date: | Sun, 14 Dec 2008 17:27:32 +0000 |
| Subject: | note 87642 deleted from function.xmlrpc-encode by danbrown | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-148158@lists.php.net to get a copy of this message | ||
Note Submitter: SneakyWho_am_i
----
QUOTE from anonymous:
"Another quirk (more of a bug i think) is the automatic encoding of hashes where all keys that
begin with a digit between 1 and 9 are lost:
http://bugs.php.net/bug.php?id=37746
Luckily I found a quick workaround. Just append chr(0x00) to your keys and the xmlrpc response will
be correct. Maybe this will apply to encoding of hashes for requests too."
Yes, that is definitely worth noting! However, it is certainly not a bug. Check out the XML spec
from w3c (creators of XML), or this simple explanation from w3schools:
http://www.w3schools.com/XML/xml_elements.asp
"[XML Element] Names must not start with a number or punctuation character"
...
So apparently XML-RPC-EPI is only generating well-formed XML - which is a GOOD thing, because of
course the receiving server should discard the document if it's not well-formed.
What is probably a bug isn't the fact that it's discarding elements, but that it's
not issuing a notice upon doing so...?