On Sep 3, 2014, at 3:36 AM, Ignasi Barrera <n...@apache.org> wrote: > I also like the syntax and think that's a pattern we could use in more > places. > > Regarding the naming I'm +1 to change the *Options to *Request or something > else to avoid confusion with the already xisting Options pattern.
The new pattern still encapsulates options for creating a resource though. The name seems appropriate. To me, createOptions() says "build me the options for creating a resource". Request is a bit generic and overloaded. In the web service world, all calls are a request. It doesn’t distinguish if parts of that request are optional or required. Everett
