From mboxrd@z Thu Jan  1 00:00:00 1970
From: Premjith Rayaroth <premjith.rayaroth@oracle.com>
Subject: Xen API  or XM
Date: Tue, 10 Apr 2007 18:01:31 +0530
Message-ID: <461B83A3.2090805@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Hi,

With the introduction of Xen-API, will 'xm' command be deprecated?  .

1. Apart from Remote/RPC calls, does Xen API have more features than 'xm' ?
2. If I compromise on the remote/RPC feature, can I still keep using 
'xm' for future releases of Xen?
3. Will 'xm' command be deprecated or discouraged as a best practice for 
the current/later releases of Xen?

Thanks
-Prem