xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Vincent, Pradeep" <pradeepv@amazon.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jackson <Ian.Jackson@eu.citrix.com>, Dulloor <dulloor@gmail.com>
Subject: Re: New feature support - xl or xm ?
Date: Wed, 9 Jun 2010 10:30:40 -0700	[thread overview]
Message-ID: <C8351DD0.17C41%pradeepv@amazon.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006091603250.3401@kaball-desktop>


[-- Attachment #1.1: Type: text/plain, Size: 1040 bytes --]

Thanks Stefano. That helps.


On 6/9/10 8:09 AM, "Stefano Stabellini" <stefano.stabellini@eu.citrix.com> wrote:

On Wed, 9 Jun 2010, Vincent, Pradeep wrote:
>
> Also, was there a compelling reason to move away from the 'xm' interface. Obviously 'xm' is both an API and an
> implementation and I certainly see the reasons to move away from libxenguest/xend/xm implementation in favor of libxl. But
> was there a reason to opt for a new 'xl' API as opposed change the implementation behind the established 'xm' API.
>
> Did the 'xm' interface (excluding the implementation) fall short of serving the needs ?
>

We like the 'xm' CLI, in fact we are trying our best to provide a
compatible command line interface with 'xl'.
Ideally you'll be able to symlink xl to xm and everything will still
work. If you find any problem with command line incompatibilities please
let us know, and we'll fix them.

On the other hand if you are speaking about the XML-RPC interface
provided by xend, that is a totally different matter.


[-- Attachment #1.2: Type: text/html, Size: 1600 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-06-09 17:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 22:37 New feature support - xl or xm ? Dulloor
2010-05-28 22:41 ` Stefano Stabellini
2010-06-01 10:20   ` Ian Jackson
2010-06-08  1:35     ` Vincent, Pradeep
2010-06-08  9:17       ` Stefano Stabellini
2010-06-08 22:49         ` Vincent, Pradeep
2010-06-08 23:37           ` Vincent, Pradeep
2010-06-09 15:09             ` Stefano Stabellini
2010-06-09 17:30               ` Vincent, Pradeep [this message]
2010-06-10 20:02               ` AP Xen
2010-06-10 20:19                 ` Keir Fraser
2010-06-09 14:43           ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C8351DD0.17C41%pradeepv@amazon.com \
    --to=pradeepv@amazon.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dulloor@gmail.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).