I’m used to having to return other records on a DELETE in Ember Data – specifically records that are relationships of the deleted record. This is necessary so that Ember Data maintains a current picture of the server-side relationships, so these can be reflected on the client.
This does not seem possible if:
204 No Content
A server MUST return a 204 No Content status code if a deletion
request is successful and no content is returned.
A server MUST return a 200 OK status code if a deletion request is
successful and the server responds with only top-level meta data.
included records aren’t allowed in the
200 OK case, so how can the client be maintained current? Should the server not manipulate relationships in this way any longer, and leave it to the client? (In other words, the relationship must be unlinked explicitly by the client before deletion??)