> this is the first instance of this "typesafe domain object options" pattern > in jclouds
I was mostly thinking about what method and class names users see when they use jclouds apis - we have Options a lot, we have Builders as well. ________________________________________ From: Ignasi Barrera [n...@apache.org] Sent: Monday, September 08, 2014 2:46 AM To: dev@jclouds.apache.org Subject: Re: Using *Options for domain objects? My preference is also "createBuilder". I. On 7 September 2014 23:37, Andrew Phillips <aphill...@qrmedia.com> wrote: >> 1) Change to createBuilder / createObject >> 2) Leave as is (createOptions) >> >> Any examples of existing code that can help steer us one way or the other? > > > I hope someone will correct me, but as far as I'm aware this is the first > instance of this "typesafe domain object options" pattern in jclouds, so I > unfortunately can't think of any :-( > > For what it's worth, my vote is for createBuilder/CreateObject ;-) > > ap
