I can appreciate the desire to clarify idempotency for users explicitly in
the API, but I'm not sure that we'll be able to do this so easily. For
example, it seems to me there are many existing POST API calls that are
actually idempotent, I can tell mesos to teardown the framework multiple
times,
As one of the developers who considered PUT, I actually feel that being
able to distinguish idempotent API calls with a PUT method at
least provides more self-explanatory semantic.
Another thing to consider is whether certain SDK which can generate client
libraries from REST API prefers PUT for
I noticed that we have some inconsistent usage of POST vs PUT (only 1
endpoint uses PUT today), so I did a little survey of our endpoints:
https://docs.google.com/document/d/1yo-ZcKAdrCwBmTDkAKGNLnhK7fAfwatKddZrhtpgyMk/edit?usp=sharing
A couple of findings:
* We often don't look at the method,
