On Thu, Mar 29, 2007 at 10:38:56AM -0400, Ray Kelm wrote:
> I'm sorry, I should have been more clear. Apache xml-rpc has support
> for vendor extensions, which violate the original xml-rpc spec. In
> order for them to be enabled, their client library negotiates with the
> server implementation, and only if both sides have extensions enabled
> does it support them. The expected situation is that if a non-apache
> client accesses an apache server, it won't ask for extensions, so the
> server will not use them. If an apache client accesses an non-apache
> server, the negotiation is ignored, so the client disables the
> One of those extensions is support for returning a null value (or
> python's None in this case) as <nil> or maybe <ex:nil>. The python
> xmlrpc code does this apparently by default, when you call a method
> that has no return value, for example, xend.domain.unpause.
xend.domain.unpause is one of the legacy XML-RPC methods, and not part of the
Xen-API. If you try VM.unpause you should get a quite different result.
Xen-devel mailing list