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/
Home Products Support Community News


Re: [Xen-API] Typing in XML-RPC

To: Daniel Veillard <veillard@xxxxxxxxxx>
Subject: Re: [Xen-API] Typing in XML-RPC
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 26 Jun 2006 11:02:56 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 26 Jun 2006 03:03:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060626092125.GB2850@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <449C3D47.6070806@xxxxxxxxxx> <20060626083407.GB787@xxxxxxxxxxxxxxxxxxxxxx> <20060626092125.GB2850@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Jun 26, 2006 at 05:21:25AM -0400, Daniel Veillard wrote:

> On Mon, Jun 26, 2006 at 09:34:08AM +0100, Ewan Mellor wrote:
> > > Another thing to consider is having a type of exception.  I like 
> > > exception based APIs (i'll say that for another email) however the 
> > > format of the standard XML-RPC exception leaves a lot to be desired.
> > 
> > I agree that we should be using exceptions, and I also agree that the 
> > exception specification is not great.  The document proposes using a string
> > array for exception code and parameters.  A binding for a language with
> > exceptions could then marshall those into first class exceptions, and that's
> > certainly the way I'd want to do it.
>   Do we have a list of those error codes, or is this something which needs
> to be defined, I don't think I saw them.

No, we'll have to define them.


xen-api mailing list

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