Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
REST API design indicates there are four resources archetypes: document, collection, store and controller.
Store do not create new resources; therefore a store never generates new URIs.
An example:
PUT /users/12245/favorites/boston-celtics
A user added Boston Celtics to his favorites list.
But how that isn’t creating a new resource ? and how it isnt generating a new URI?
A store does not create a resource on its own. The user of the store creates endpoints / URIs.
The contrast is between a Collection and a Store
Collection
A collection resource is a server-managed directory of resources. Clients may propose new resources to be added to a collection. However, it is up to the collection to choose to create a new resource, or not. A collection resource chooses what it wants to contain and also decides the URIs of each contained resource.
Store
A store is a client-managed resource repository. A store resource lets an API client: put resources in, get them back out, and decide when to delete them.