OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   A critique of XML-RPC

[ Lists Home | Date Index | Thread Index ]
  • From: John Cowan <cowan@locke.ccil.org>
  • To: xml-dev@ic.ac.uk
  • Date: Sat, 6 Feb 1999 23:33:16 -0500 (EST)

I have read the XML-RPC specification
at http://www.scripting.com/frontier5/xml/code/rpc.html with great
interest.  I have the following issues with it:

1) There is no support for internationalization, despite the
support present in XML.  Since the MIME type is text/xml
(as opposed to application/xml), the character encoding is
US-ASCII unless overridden.  No mention is made of support for
character references like &#x2020; (DOUBLE DAGGER).

I would suggest supporting either "text/xml; charset='utf-8'".
In addition, the references to "ASCII" in the spec should be changed.

2) There is no support for integers longer than 32 bits.

I suggest allowing <int> values to be arbitrarily large, reserving
the <i4> tag for 32-bit signed values.  This would be an upward
compatible extension for senders; receivers would have to check
whether <int> data was in fact within the 32-bit signed range
if backward compatibility is desired.

3) Floats are fairly useless because no rules exist for setting limits.

I suggest that no receiver be allowed to reject a value which can be
represented in 32-bit IEEE floats: between 1e-149 and 1e104, positive
or negative, or zero.

4) The statement that "A string can be used to encode binary data"
cannot be true, because arbitrary binary data cannot appear in XML
documents: there is no way to represent bytes of value 0-8, 11-12, or
14-31.  This is only a documentation consideration, as the base64
element does allow the representation of arbitrary binary data.

5) The very limited fault struct means that more complex exceptions
such as Java, Python, or C++ support must be flattened into strings
for return to the client, even though XML-RPC has ways of encoding more
complex objects.

I suggest allowing a struct within a fault object.

John Cowan					cowan@ccil.org
		e'osai ko sarji la lojban.

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS