Closed martinei closed 9 years ago
Applies to not yet used IDs, too. I guess we should return a 404 instead of a NPE.
I'd return an HTTP 410 Gone
. ;)
How do you decide if the resource was once there? We would need to keep a list of previously used IDs just to decide between 404 and 410...
That's an easy one: Go for Soft deletion
! :grinning:
Maybe I'm to pragmatic but just to decide between 404 and 410?
Maybe I should have used this emoji instead: :trollface:
Well, it depends on the storage solution, but I would avoid Soft deletion
if there is not a business case for it. Personally I'm totally fine with a 404
not found.
Oh! And i was under the impression we are in the age of "keep everhtyingh" , don't save state but actions. Would a "deleted" Flag be that hard? The semantic difference between "you idiot that site does not exists" and "I'am sorry, someone took this down" is big enough to justifiy it. Just my 2c.
If one creates a Update and later removes it the url should says somehtingh like "This Update was deleted". Currently it renderes a Nullpointer. Since URLs a propagated via RSS + Mail we must keep those URI alive event after deletion.