Comment 8 for bug 1353670

The trick is knowing when 'delete' deletes the underlying physical resources (normal case) and when it doesn't (abandon case). That's requires either a state change in the export phase or a parameter passed to the delete phase. I'm relaxed about which it is, although I think it's somewhat unusual to be passing data with a DELETE request in a ReST API.