WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH] Fixup a couple of problems with XML-RPC error ha

To: Anthony Liguori <aliguori@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] Fixup a couple of problems with XML-RPC error handling
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 24 Mar 2006 13:40:27 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 24 Mar 2006 13:42:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <44230452.7000703@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <44230452.7000703@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Thu, Mar 23, 2006 at 02:25:54PM -0600, Anthony Liguori wrote:

> This fixes a number of problems introduces in the recent XML-RPC 
> check-in.  The higher level errors are a great idea and I've also 
> extended it a bit to have a slightly nicer interface.  Please apply.
> 
> Regards,
> 
> Anthony Liguori

> # HG changeset patch
> # User anthony@xxxxxxxxxxxxxxxxxxxxx
> # Node ID e4c39bd3fb27129532d55f7bb30c800143b390b3
> # Parent  8f722ac17efa4ba84eb6c678c7f33dab82fceb3e
> 1) Introduce new exception type XendInvalidDomain that maps to the high level
>    XEND_INVALID_DOMAIN faultType.
> 2) Fix exception logic in XMLRPCServer
> 3) Fix TCP server
> 4) Remove catching of ProtocolError in main.py.  ProtocolErrors only occur
>    when there is an exception in the exception handling code which shouldn't
>    ever happen.  I've reproduced the error cases described by Ewan with
>    xend_domain_setTargetMemory and once I fixed the exception logic, I get a
>    normal faultType of 1 as would be expected.
> 
> Signed-off-by: Anthony Liguori <aliguori@xxxxxxxxxx>

Applied, thank you.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>