URI for RESTful Web Services

Question

I'm trying to understand how URIs are supposed to look like. Looking at this reference: http://en.wikipedia.org/wiki/Representational_State_Transfer#RESTful_web_services, I am a bit confused by how POST is supposed to work.

The example given is this: http://example.com/resources/142. I'm associating "142" as a specific item in "resources" (thus, one could delete, update, or get the representation). The "142" is confusing to me in the context of creating a new member of a collection. What does the 142 mean? In terms of databases, would that be the new member's id? (I'm associating these with CRUD).

Can anyone clarify?

Answer 1

The example is probably a bad one. A better example in your case would be

http://example.com/users/142

In REST, this is interpretted the same as

http://example.com/users?id=142

as long on the server side you deal with the fact that the last part of the route is associated with an ID.

Both of these would identify the user 142. However, you would not generally use this with a POST, because POST is used for creation and you would not know the ID of the user you are creating at this point in most cases.

Answer 2

In your example, I would think of 142 as the resource name. Your POST might make new instances of "142" with their own id.

Answer 3

I'm not quite sure I understand either, but I understand that if you POST to http://example.com/resources/142 you are treating 142 as if it were a collection in it's own right and would be adding another item to that collection.

If it were www.blog.com/blog/142

142 might be a users blog and a POST would possible create a new Blog Post.

a PUT to 142 would either Update the whole of 142 or create the blog if it didn't exist.