One of the benefits I saw to this API was that it was trivial to support both compressed and uncompressed documents through the same message by having a flexible parameter list.
On Monday, April 29, 2002, at 07:10 AM, James Bates wrote:
Supplementary question:
* Did you do away with the idea of sending compressed DOM's accross the XML-RPC interface and
have them uncompressed on the client? I can only find a GetDocument method in the server interface
that returns an expanded, serialized DOM...
James-----Original Message----- From: James Bates Sent: 29 April 2002 15:43 To: [EMAIL PROTECTED] Subject: some more XML-RPC questions
While implementing XML:DB interfaces:
* Does Xindice have any notion of "BinaryResource"? The XML-RPC server doesn't export any, but then when checking in org.apache.xindice.core.collection, nor does the Xindice engine itself.
* Are we keeping the XML objects? If so, where do they fit into XML:DB? Into a separate service (as was the case in the CORBA client)
James
Kimbro Staken Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ Apache Xindice native XML database http://xml.apache.org/xindice XML:DB Initiative http://www.xmldb.org
