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-users

Re: [Xen-users] xend http interface

To: veillard@xxxxxxxxxx
Subject: Re: [Xen-users] xend http interface
From: Anand <xen.mails@xxxxxxxxx>
Date: Mon, 2 Jan 2006 19:40:42 +0530
Cc: Jean-David Silberzahn <jds@xxxxxxxxxx>, Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 02 Jan 2006 14:15:47 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=T5T3L2nfmB3eyryp/ojAGvwvOWncLVYA2ISBR85mJj4szddZIvL8QVRWpzFcJ89g4uXwW4w3y1nyxi5xppa6G8Pg9vsREwDRAWOJxRv5BTkiprI8UsiAKT7eleUQxC5TeRZcojHi95WAuNJc16xPdTUI0aNq8u8+9SoagnOk+SU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060102140325.GJ31254@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <acb757c00512301017q16cda192g40927118ccbb5924@xxxxxxxxxxxxxx> <43B8FBCD.3030306@xxxxxxxxxx> <acb757c00601020506k58f849f2n102e8ac5b0433a3a@xxxxxxxxxxxxxx> <43B92DE9.8030605@xxxxxxxxxx> <20060102140325.GJ31254@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>The simplest way is probably to read the xend source code to get
>an exhaustive list, the problem is that as long as it's not
>'officially' documented, I'm afraid you can have garantee that
>the interface or its semantic won't change.

This is what i fear about. If the specs change after i have used them in my application, it would be a disaster. Looks like i would be better off creating my own interface even for that matter, it will take some time, however can gurantee that specs won't change.

>  Anthony Liguori also suggested last month the possibility to add an
>XML-RPC interface, which would certainly make it easier to use in a
>variety of environments (at the expense of slightly more CPU usage I
>guess) and feel more confident about this being a supported interface.

That would be really nice, ofcourse as you said on the expense of slight cpu power. However for that flexibility many people might consider the cpu power less expensive ;)

regards,

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