It feels a little cleaner to me to have the content ID as a URL path parameter for the content PUT call. It's more consistent with the other content handlers and with standard PUT semantics (as I understand them). It also lets us treat the entire request body as the document to store, which is more convenient.
It feels a little cleaner to me to have the content ID as a URL path parameter for the content
PUTcall. It's more consistent with the other content handlers and with standard PUT semantics (as I understand them). It also lets us treat the entire request body as the document to store, which is more convenient.