Timeline for answer to How to design a RESTful API with good performance by Doval
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2015 at 15:47 | comment | added | Cormac Mulhall | There is no issue with a resource being at two URIs. For example you can have myweatherapp.com/today and myweatherapp.com/2015/feb/09 point to the same resource. A URI should only point to one resource, but a resource can have multiple URIs pointing to it. | |
| Feb 7, 2015 at 15:42 | comment | added | Javier |
@EsbenSkovPedersen, no: /api/foos/?page=1 is the first page of the container, it should be a list of elements. /api/foos/1 is one element and still the 'real' URL of the resource.
|
|
| Feb 7, 2015 at 10:42 | comment | added | James McLeod | But you can look at it as two different (not independent) resources - you just need to twist your nomenclature slightly so "resource" is not the same thing as "entity." | |
| Feb 6, 2015 at 20:19 | comment | added | Esben Skov Pedersen | But conceptually the same entity is at two different URIs now both in /api/foos/?page=1 and /api/foo/1 , but I see what you are saying and it makes sense if we see it like that. | |
| Feb 6, 2015 at 20:12 | history | answered | Doval | CC BY-SA 3.0 |