Timeline for answer to Can REST resources represent behaviour? by Robert Bräutigam
Current License: CC BY-SA 4.0
Post Revisions
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2021 at 14:46 | comment | added | Robert Bräutigam | If you're building a RESTful HTTP application, you are limited to using the existing HTTP verbs. But, a well written client shouldn't even know about that. It should only know about specific Media Types and how to process those. Then again, I'm talking about how it should work, not how most projects do it. I mean, Stackoverflow is a HTML-based RESTful App, using only 2 verbs, GET and POST. Did that bother anybody? Was that really a limitation? | |
| Jun 17, 2021 at 14:01 | comment | added | Hans | Okay so we live in a world of CRUD, and for a second there I thought we might actually use REST to do more elaborate stuff, which the quote seems to suggest is possible. I don't really understand what you say about endpoints (=resources) being behaviour in all these cases. If they all were behaviour, why would people still be complaining that REST limits them to a set of 4 verbs to implement the behaviour of their apps. | |
| Jun 17, 2021 at 13:44 | history | answered | Robert Bräutigam | CC BY-SA 4.0 |