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

[Xen-API] why not WSDL

To: <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] why not WSDL
From: "Aggarwal, Ajay" <Ajay.Aggarwal@xxxxxxxxxxx>
Date: Fri, 10 Jul 2009 11:58:57 -0400
Delivery-date: Fri, 10 Jul 2009 09:00:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoBd1Uxjass7ebFRM2WXjdfCBpt7Q==
Thread-topic: why not WSDL

Folks,

 

I am relatively new to this XEN API, so maybe this has already been discussed but I could not find any reference of it so far. I was wondering why not support WSDL and schema instead of simple XML-RPC interface. With WSDL, there are tools available to automatically generate client side stubs in different languages.  But with XML-RPC one has to manually create the client side bindings.

 

With all the tools available today, it’s so much easier to work with WSDL and schema both on the client and server side. I was wondering why the open source Xen as well as Citrix is still sticking to the *old* XML-RPC interface.

 

Any thoughts?

 

-Ajay

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api
<Prev in Thread] Current Thread [Next in Thread>