title: RESTful delete strategy
body: <p>Let's say I have a resource that can have two different behaviors when delete is called</p>
  
  <ol>
  <li>The resource is deleted. </li>
  <li>The resource is moved to the recycle bin.</li>
  </ol>
  
  <p>How would model it in a REST compliant way?</p>
  
  <p>I thought about the following solution:</p>
  
  <pre><code>DELETE /myresource     
  </code></pre>
  
  <p>moves the resource to the recycle bin (default behavior)</p>
  
  <pre><code>DELETE /myresource?force-delete=true  
  </code></pre>
  
  <p>forces delete on the resource.</p>
  
  <p>Is that REST compliant? I have never seen query parameters in the URL when calling DELETE, is that OK?</p>