I would tend to disagree. A "bulkdeleter" is a thing. It's a virtual thing but so are most other "resources". And putting the links of the resources to be deleted in the body seems to me to follow the HATEOAS precepts of REST.
Paul Morris On Jul 29, 2013, at 2:22 PM, "Stephan Koops" <[email protected]<mailto:[email protected]>> wrote: Hi, the bulk deleter is not restful. A URL should describe a thing, not an action. But there is another solution: You could create a resource, that represents multiple customers: /customers/1-22-65-75 1, 22, 65 und 75 are e.g. the primary keys in the database. That Resource could be loaded (e.g. a link to the details) and it could be deleted. DELETE /customer/1-22-65 best regards Stephan On Thu, Jul 25, 2013 at 7:30 PM, dbaq <[email protected]<mailto:[email protected]>> wrote: Hi Fabian, This is almost what I want. Here is what I want : POST /bulkdeleter ["/customer/1", "/customer/22", ...] From my /bulkdeleter I want to execute DELETE /customer/1 and get the response then I want to execute DELETE /customer/2 and get the response. Then I want to return from /bulkdeleter the list of responses formatted in JSON (error or not) How can I do that ? This message and any included attachments are intended only for the addressee. The information contained in this message is confidential and may constitute proprietary or non-public information under international, federal, or state laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3061571
