We use CBVs too, but I guess it depends how you implement them. We don’t explicitly use

DeleteView

etc, but instead have

get

,

put

,

delete

methods within one class. I definitely prefer Method 2 for simplicity, but I do agree that method 1 may have better atomicity. What do you mean by “having to deal with the UI between 2 requests” for method 2? I understand that there are 2 requests, the delete then the subsequent list update, but what challenges does that pose to the UI in between? It should be as simple as the delete view deleting the item from the DB, then the list view updating the list with the latest data, right?