Re:Show HN: Deck of Cards – A playing card API
by vladharbuz on Monday May 11, 2015 @04:59AM
(#9523422)
I agree with your comments and take them as evidence that REST is exceedingly difficult and complex for these use cases.
You can create new resources, just as I have, it just doesn't make sense to "POST /cards" when you're not making a new card at all.
Commenting directly on you suggestions:
This means each DELETE on this url would result in a different deck state which isn't idempotent as DELETE is mean to be. Same with this, the resource would end up in a new state each time making it unsafe to do repeatedly as the HTTP spec says.I think the issue is REST is taught with a CRUD view point and people have difficulty thinking about it in other ways. Also the English meanings of the HTTP verbs get confused with their HTTP meanings which doesn't help.
I liked this blog post which talks about the concept of "REST without PUT".
http://www.thoughtworks.com/insights/blog/rest-api-design-re...
edit: you've edited you comment since I started my reply:
I like your idea of replacing shuffle with a new deck:
You could then do things like lock the source deck which would make it easier to implement a multi-client system where you cannot draw from a deck until you have been informed it has been shuffled.