Containers: specify behavior on deleting non-empty containers

[bjdmeest]

possibly related to #87

Should it be possible to delete a container that is non-empty?
What if you have a full path of this/is/an/entire/subtree/that/does/should/be/removed/old.txt to delete?

[TallTed]

Similar to UNIX-like environments, I would say it should be "possible to delete a container that is non-empty", probably with an extra flag or two on the delete request (e.g., rm -rf which deletes r[ecursively] with a f[orce], or rm -r which deletes r[ecursively] with a confirmation of each item as it's encountered).

The answer to "What if you have a full path of this/is/an/entire/subtree/that/does/should/be/removed/old.txt?" is left as an exercise for the reader.

[laurensdeb]

@bjdmeest Could you look at whether the Depth: Infinity approach currently proposed in the text suffices to address your needs here. https://w3c.github.io/lws-protocol/lws10-core/#delete-resource