From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: Xen Management API Draft, version 0.4 Date: Fri, 07 Jul 2006 16:10:56 +0100 Message-ID: <1152285056.7717.118.camel@localhost.localdomain> References: <20060703155332.GA5002@leeni.uk.xensource.com> <1152278206.7717.47.camel@localhost.localdomain> <20060707131934.GA24259@leeni.uk.xensource.com> <1152280150.7717.69.camel@localhost.localdomain> <20060707143136.GA20865@leeni.uk.xensource.com> <1152284231.7717.113.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1152284231.7717.113.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Besides, if you get good coverage in the use-cases you consider to start off with then you'll end up with a good dynamic model that implements a set of primitive operations that are useful and flexible which it will be possible to recombine to implement a substantial proportion of unforseen use-cases without having to make any API changes.