News for hackers. Stuff that matters.

A comment on Show HN: Deck of Cards – A playing card API. Parent comment

Re:Show HN: Deck of Cards – A playing card API by jalfresi on Monday May 11, 2015 @06:54AM (#9523759)
DELETE a card from the deck. Return the card(s) drawn in the response body. Have a separate resource for the top of the deck:

DELETE /api/<deck-id>/top?count=2

------

200 Ok

8♣

10♥

[ Parent | on HN ]
Re:Show HN: Deck of Cards – A playing card API by hartror on Monday May 11, 2015 @07:00AM (#9523772)
DELETE is idempotent to quote a Stack Overflow answer on the subject:

> Idempotence refers to the state of the system after the request has completed

> ...

> The key bit there is the side-effects of N > 0 identical requests is the same as for a single request.

http://stackoverflow.com/questions/4088350/is-rest-delete-re...

[ Parent | on HN ]
Re:Show HN: Deck of Cards – A playing card API by jalfresi on Monday May 11, 2015 @08:38AM (#9524191)
The example I gave is idempotent. Calling it n >0 times would result in the same side effects.
[ Parent | on HN ]
Re:Show HN: Deck of Cards – A playing card API by couchand on Monday May 11, 2015 @08:50AM (#9524260)
That's not what idempotent means. It doesn't mean it produces the same side effects every time, it means multiple calls are equivalent to a single call.
[ Parent | on HN ]
Re:Show HN: Deck of Cards – A playing card API by jalfresi on Monday May 11, 2015 @09:03AM (#9524342)
Gah! You're right. In that case POST would be the only acceptable option here.
[ Parent | on HN ]