4 ms·
There is a real need for this in collection oriented REST interfaces. While PUTing the individual properties is possible, it doesn't allow you to 1) Commit
by kogir 17y ago
There is a real need for this in collection oriented REST interfaces. While PUTing the individual properties is possible, it doesn't allow you to
1) Commit a set of changes together as a single transaction
2) Commit a set of changes in a single HTTP request (latency matters)
And yes, you can just PUT the whole thing, unless one of the properties you aren't updating is a 4MB image, or 500MB video.
I'm working with a REST framework where the authors have been forced to use a custom verb (MERGE) to provide this functionality. See http://www.odata.org/developers/protocols/operations http://www.odata.org/developers/protocols/operations
- psadauskas 17y agoSo why not just separate the video from the metadata? The PUT would a be small thing thats easy to replace, and contains a link to the video elsewhere.
- kogir 17y agoOk, bad example. Imagine an item for sale that has 100KB of text as a description. Does it really make sense to link to the description text rather than keep it along with the name, price, etc? Does it make sense to update it every time from say, a mobile client?
- _delirium 17y agoThat set of use cases (adding semantics for resource modification to HTTP) is pretty much what WebDAV was designed for, wasn't it?