From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: Xen Management API Draft, version 0.4 Date: Fri, 7 Jul 2006 14:19:34 +0100 Message-ID: <20060707131934.GA24259@leeni.uk.xensource.com> References: <20060703155332.GA5002@leeni.uk.xensource.com> <1152278206.7717.47.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1152278206.7717.47.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: Harry Butterworth Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Jul 07, 2006 at 02:16:45PM +0100, Harry Butterworth wrote: > I may be misreading the document but it seems to me like you've > constrained the class definition such that all of the construtor > parameters have accessor methods. > > I think this may be a bit unnatural and I think any required accessor > methods for constructor parameters are just a special case of accessor > methods required in general and they in turn are just a special case of > general purpose methods like the ones required to drive the vm > lifecycle. You've lost me. Could you give an example? Ewan.