On Fri, Jan 29, 2010 at 2:45 PM, Haron Media <[email protected]> wrote: > > On 01/29/2010 11:14 PM, Vladimir Dronnikov wrote: >> May be "Server-side has a separate queue for queries-for-deletion; to >> push such a query, a request should be made as POST <URI>/delete"? >> > > Precisely my point. That or using PUT to alter the state of the document > to deletable, before actual DELETE is issued.
More generally, a request activates a temporary "permission to delete this resource" flag. This will be necessary for some cases. It's not RESTful. But the two requirements are contradictory, so one will have to supercede. Either it's acceptable to delete the resource at any time (without confirmation), or it's not. If it is, a simple DELETE action is sufficient. If not, the delete has to be protected behind a confirmation or nonce. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
