Jerome Louvel <contact <at> noelios.com> writes: ...
> It could also clarify things by renaming "post(Rep.)" to > "postRepresentation(Rep.)" to be more consistent with > "getRepresentation(Variant)" namine and to reduce the confusion with > lower-level Uniform handle* methods. > > What do you think? What is your ideal design for the Resource class? I think *Representation is problematic: headRepresentation()? I understand your concerns with get(Variant), getVariant(). A colleague of mine pointed out that conceptually, merely using post(), get(), etc., is like encroaching on a global name space. He suggested (and I'm comfortable with), doPost(), doGet(), doHead(), doDelete(), doPut(), and doOptions(). The 'do' has the effect of taking the names out of the global name space...conceptually. Sean
