All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: Ewan Mellor <ewan@xensource.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen Management API Draft, version 0.4
Date: Fri, 07 Jul 2006 14:16:45 +0100	[thread overview]
Message-ID: <1152278206.7717.47.camel@localhost.localdomain> (raw)
In-Reply-To: <20060703155332.GA5002@leeni.uk.xensource.com>

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.

A bit of googling turned up this article on accessors which I tend to
agree with for the most part:

http://www.javaworld.com/javaworld/jw-09-2003/jw-0905-toolbox.html

Harry.

  parent reply	other threads:[~2006-07-07 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 15:53 Xen Management API Draft, version 0.4 Ewan Mellor
2006-07-04 11:55 ` Harry Butterworth
2006-07-07 12:18   ` Harry Butterworth
2006-07-07 13:22     ` Ewan Mellor
2006-07-07 14:32       ` Harry Butterworth
2006-07-07 13:16 ` Harry Butterworth [this message]
2006-07-07 13:19   ` Ewan Mellor
2006-07-07 13:49     ` Harry Butterworth
2006-07-07 14:31       ` Ewan Mellor
2006-07-07 14:57         ` Harry Butterworth
2006-07-07 15:10           ` Harry Butterworth

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=1152278206.7717.47.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=ewan@xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.