Timeline for Designing a REST API with resource relationships?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2018 at 20:34 | comment | added | Kwebble | @Christophe It may not be the final answer to the question, but it was the best I could do with the available information. The question seems to focus on URL's. I'm saying it's more important to define the API depending on the requirements and gave a few options without knowing those details. For example: what if this API is for a soccer application with multiple server backends to handle all teams of the world? Or is there only 1 client, directly linked to 1 API implementation. In that case REST might be overkill and exchanging unspecified blobs of JSON is good enough. | |
| Aug 27, 2018 at 22:40 | comment | added | Andy | @Christophe The question is general though too; should you return links or the actual data? This answer is saying it depends on what you typically expect clients to need, which IMO is spot on. | |
| Aug 26, 2018 at 22:23 | comment | added | Christophe | Your contribution suggests that you have good ideas on REST APIs. However, after having read it several times, I have the feeling that if could be too general and I'm still not sure if it really answers the question. Could you elaborate a little bit and refer explicitly to the different approaches of the questions in order to avoid misunderstandings ? | |
| Aug 26, 2018 at 21:38 | history | answered | Kwebble | CC BY-SA 4.0 |