Should calling delete on a non-existent instance just be silently ignored?

[carsonfarmer]

Right now, this throws an error, but should it? For remote clients that don't know ahead of time if an instance has already been deleted, it would be useful if this just failed silently. Either way the instance is no longer in the collection. Are there unexpected consequences to this that we need to consider? Now that we have errors coming back from transactions, maybe this isn't such a problem?