uri scheme, and I feel like I hit a point of transcendence recently when I decided how to record a user
staring a story.
- PUT /article/:articleID/favorite/:userID
- DELETE /article/:articleID/favorite/:userID
that POST didn't make sense, as you couldn't really favorite a story more than once at
a time, and of course DELETE makes sense here. Adding them as a relation between the article and the user
seems to make sense in this URI scheme as well.
So, all in all, I'm proud of myself.
Despite it being such a tiny, simplistic thing.
I hear ya. I came across a similar situation while I was writing my own REST API (inReplyDelete
Python) for a Google App Engine Datastore.
I'm planning to eventually build
it out into a complete inventory tracking system. At one point I was trying to figure out how to update/add
multiple items at once when I finally realized what the differences between POST and PUT just sort of
It's amazing how under-appreciated REST is out in the working
world. If you're interested in reading more about it I suggest you take a look at
http://timelessrepo.com/haters-gonna-hateoas. It's a timeless gem that I stumbled on in the 'popular'
section of Pinboard.