API overview doc : Put vs Patch

Question

API overview doc : Put vs Patch

nthomas-redhat opened this issue 8 years ago · comments

While going through the document, observed that 'PATCH' is not present in the supported HTTP verbs list. In some cases(like editing only certain parameters of a resources ) , I feel that PATCH can be used over PUT as you it is generally used for replacing a resource.

Is there any specific reason why PUT is proposed for update operations?

Nishanth Thomas · Answer 1 · Sat Oct 01 2016 14:19:45 GMT+0800 (China Standard Time)

@anupnivargi , Can you please comment on this?

Nishanth Thomas · Answer 2 · Sat Oct 01 2016 14:26:08 GMT+0800 (China Standard Time)

Also there is a mention about rate limiting? How you plan to implement this?

Anup Nivargi · Answer 3 · Mon Oct 03 2016 03:50:32 GMT+0800 (China Standard Time)

@nthomas-redhat since the http methods are generated from the YAML files, we would have to specify the difference of PUT and PATCH in it, today it says 'update', which is mapped to a PUT which supports full resource updating or a single attribute, but we can surely discuss this if its a issue.

Regarding rate limiting, I don't think we are going to have a hard limit as of now, since we need to come up with the numbers depending on the load and servers etc, so I have not added anything regarding it.

Nishanth Thomas · Answer 4 · Mon Oct 03 2016 16:25:32 GMT+0800 (China Standard Time)

Thanks @anupnivargi . yes I think single attribute(or partial resource updates) updates should be handled by PATCH and PUT should be used only when you have a full resource update. Sure, we can discuss about this