On Tue, Nov 29, 2011 at 11:55 PM, Mark Kharitonov <[email protected] > wrote:
> 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. > POST implies creating a new user. This means the resource you are operating on is the **list of users**, since the resource for the new user does not exist until after the POST operation. You can't operate on your resource until it exists :) > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2889231 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2889493
