title: REST DELETE idempotency
body: <p>Given a DELETE request that will delete resource at an integer index, does the possibility of recreation of a resource at that index break strict idempotency?</p>
  
  <p>e.g. a DELETE request is made to /api/resource/123 deletes the resource at 123. Then a post request is made which creates a new resource which can be retrieved by a GET request to the same url. </p>
  
  <p>It seems to me that for the original DELETE to be properly idempotent, the API should never create a new, different, resource with a previously used id, but I can't find a clear reference.</p>