From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrick O'Rourke <porourke@egenera.com>
Subject: Re: An Introduction to the Xen-API Work
Date: Wed, 08 Nov 2006 14:22:58 -0500
Message-ID: <45522E92.4000007@egenera.com>
References: <20061104152907.GD28706@leeni.uk.xensource.com>	<4552221D.1080705@egenera.com>
	<20061108184556.GD32530@leeni.uk.xensource.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>
In-Reply-To: <20061108184556.GD32530@leeni.uk.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: Ewan Mellor <ewan@xensource.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Ewan Mellor wrote:

> Would you like an API call that better supported this use-case?  In the long
> run, might your integration be easier if Xend supported "save to this
> address/port" or something like that?

Yes, I believe that would suit our needs.

Pat

-- 
Patrick O'Rourke
porourke@egenera.com