Timeline for REST API - omitted properties in POST request: How should they be handled?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot | replaced http://stackoverflow.com/ with https://stackoverflow.com/ | |
| Feb 13, 2016 at 16:37 | comment | added | bigstones | @RichardDesLonde in general yes, but not in OData <= 3.0 (didn't check 4.0). | |
| Feb 13, 2016 at 1:07 | comment | added | richard | POST and PUT can both create, but in completely different ways. POST will create a resource, but the resultinig URI of the new resource is determined by the server. PUT creates a resource, but at a specified (by the client/request) location. | |
| Feb 12, 2016 at 18:20 | history | edited | bigstones | CC BY-SA 3.0 | clarifications |
| Feb 12, 2016 at 18:19 | comment | added | bigstones | @gnasher729 I have no idea of why I wrote that, sorry. It meant something, this morning... | |
| Feb 12, 2016 at 8:28 | comment | added | gnasher729 | Why? The client can easily delete missing properties by passing a null value. What you suggest forces the client to keep track of all properties, even those that the client isn't interested in at all, and to send them back to the server if all they want to do is change one single property. I would find that kind of API annoying to the extreme. | |
| Feb 12, 2016 at 7:14 | history | answered | bigstones | CC BY-SA 3.0 |