3 ms·
Wouldn't be RESTful.
by MatthewPhillips 14y ago
Wouldn't be RESTful.
- mistercow 14y agoYes, but for the current clients (and proxies) in the wild, and under the specific circumstances in question, REST is is a broken architectural style. Fundamentally, the purpose of a RESTful API is to have a standard organization of operations so that REST-familiar users automatically understand the general flow of the interface. The matter of specifying the CRUD operation via HTTP methods or via a separate parameter is an implementation detail. Is anyone seriously going to trip on your interface if you say something like "This API is essentially RESTful, but everything goes through POST and the CRUD operation is specified by the "op" POST parameter"?
- MatthewPhillips 14y agoI don't have a strong opinion on whether that's a good way to do it or not, but it's definitely not RESTful. The question I would have is whether it is ok to put your GET parameters in the body, which is generally frowned upon, but might be acceptable in this extreme circumstance.