• Welcome to Valhalla Legends Archive.
 

Empty Strings in XML-RPC

Started by Mr. Neo, May 18, 2005, 07:37 PM

Previous topic - Next topic

Mr. Neo

In XML-RPC, how does one go about handling an empty string?  The official spec doesn't say anything about it.  From what I've seen in several implementations of XML-RPC, the clients are only parsing for <string></string> as an empty element.  I know in XML you could do <string/>.  Would this be legal in XML-RPC?

An example would be:
<member><name>errors</name>
<value><string/></value></member>

Is this legal?  Or should it read:
<member><name>errors</name>
<value><string></string></value></member>

Any input on the issue would be great.  Also, any links to some sort of spec on how to handle an empty string would be appreciated.

Best,

MyndFyre

I've generally seen null values represented in XML as <string /> and empty strings as <string></string>.
QuoteEvery generation of humans believed it had all the answers it needed, except for a few mysteries they assumed would be solved at any moment. And they all believed their ancestors were simplistic and deluded. What are the odds that you are the first generation of humans who will understand reality?

After 3 years, it's on the horizon.  The new JinxBot, and BN#, the managed Battle.net Client library.

Quote from: chyea on January 16, 2009, 05:05 PM
You've just located global warming.