I agree that the xml-rpc is an implementation detail. Our project cannot guarantee that implementation details will not change. XML:DB is our guarantee, so I'm +1 for supporting that API.
-Kevin Ross -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Kevin O'Neill Sent: Wednesday, August 06, 2003 6:37 PM To: [EMAIL PROTECTED] Subject: Changing the format of the document returned via an XML-RPC query At the moment there are a number of bugs in the xml-rpc driver rooted in the approach taken to format of the query response document. Currently the response nodes are added to an xml document then this document is serialised to text. This causes a flattening of the nodes and text nodes are merged. There's also an issue with attribute nodes being returned as they can't be added as a node on the document element, so they fail. My proposal is to change the result document so that these issues are taken care of (the example xml has been typed as I thought, so please feel free to fix any typos or inconsistencies). <result xmlns="http://xml.apache.org/xindice/ns/query-response/2.0";> <element><foo xmlns="http://foo.example.net"/></element> <attribute ns="http://foo.example.net"; localname="bar" prefix="bar">value</attribute> <text>Hello world</text> <boolean>true</boolean> <string>hello</string> <number>27.0</number> </result> The downside is that this would break compatibility with any third party drivers using our internal xml-rpc protocol. It would get us up and running though :). Thoughts? -k
