> DELETE /image/<ID>/prop or POST /image/<ID>/prop call in Diablo?
I think you're right, a lot of the current messiness surrounding Image properties would go away if we adopted full REST semantics. To me (not necessarily Roy Fielding ;-), this would mean:
* NOT using headers to store or retrieve image-metadata. Rather, we would use standard GET, POST, PUT, and DELETE operations for each of these.
* Image-properties would be a resource mounted at either /image/1/property/2 or /image-property/2.
There pros and cons to both, but in terms of routing, the latter approach ends up being much simpler.
> DELETE /image/<ID>/prop or POST /image/<ID>/prop call in Diablo?
I think you're right, a lot of the current messiness surrounding Image properties would go away if we adopted full REST semantics. To me (not necessarily Roy Fielding ;-), this would mean:
* NOT using headers to store or retrieve image-metadata. Rather, we would use standard GET, POST, PUT, and DELETE operations for each of these.
* Image-properties would be a resource mounted at either /image/1/property/2 or /image-property/2.
There pros and cons to both, but in terms of routing, the latter approach ends up being much simpler.
Thoughts?