Timeline for Best way to enable field removal through PATCH
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2023 at 19:23 | comment | added | VoiceOfUnreason | Conditional requests are the right tool to use for avoiding the lost edit problem, not changing request semantics. The other objection seems to confuse resource representations with other concerns - hard to be sure via low bandwidth communication. | |
| Jun 20, 2023 at 17:47 | comment | added | Kevin Matheny | A good reason not to PUT the replacement is that you may not have the full set of information, or you may not have confidence that your representation is up to date. For a resource that is being updated, even if you implement a GET followed promptly by a PUT, there is a chance that you will overwrite updates. PATCH is safer in these cases. | |
| Sep 17, 2021 at 5:31 | comment | added | Andy | This is unnecessarily verbose and extremely complicates stuff when you are using accept headers for versioning and perhaps even routing to backends. | |
| Sep 17, 2021 at 3:14 | history | answered | VoiceOfUnreason | CC BY-SA 4.0 |