Why do you say that the POST operation applies to the Users resource? I was thinking that I do POST of a User resource, hence the POST operation applies to the User resource. But I also understand your reasoning, because one can say that POST of a User resource affects some Users resource.
However, I want to be free to decide how to treat the POST request and usually I find it more convenient to keep it bundled together with the GET, PUT and DELETE because together they form the CRUD of a single entity type - User. And here I am forced to split the CRUD into C and RUD, because of the constraints of the underlying framework. Previously, I have worked with the OpenRasta framework (.NET), which does not impose such limitations. Your advise about refactoring the argument verification code is valid and well understood. Again, I must have been spoiled by OpenRasta, which does allow to have strongly typed request handler methods, eliminating the need for the boring boilerplate code having to do with argument verification. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2889231
