RESTful delete strategy

Question

Let\'s say I have a resource that can have two different behaviors when delete is called

1. The resource is deleted.
2. The resource is moved to the recycl

Answer 1

A pure REST strategy should prefer non changing resources. In my opinion, you are not changing the resource by appending a parameter, so it sounds like good strategy to me.

If you were to perform the same action like so:

DELETE /myresource.force

that would act like another resource, which wouldn't be optimal.