Andrew wrote:

Caching is an interesting problem. Who can know whether a given XML-RPC method is returning relatively static data that's constant for several hours, or transient data that changes a lot? Only the XML-RPC server, and maybe the caller, can know this. I don't think a solution is possible until XML-RPC supports some way to signal whether a method's results are cacheable or not, so I don't think caching is possible at this point in time.

Aren't HTTP headers appropriate for this? That is, don't think of it as part of the payload (XML), rather the transport (HTTP). Make the XMLRPCMethod have caching policies controlled by the various HTTP/1.0 (or 1.1) HTTP headers. Just my two cents. --Paul Paul Everitt Digital Creations paul@digicool.com 540.371.6909 ----------------------------------------- The Open Source Zope application server http://www.zope.org/