Resource Routes - PUT vs PATCH

Resource Routes - PUT vs PATCH

natanfelles
Member
Posts: 136
Threads: 24
Joined: Jan 2016
Reputation: 8

07-20-2017, 06:15 PM

Assuming that PATCH makes it possible to update one attribute at a time while the PUT forces the update of the entire entity.

Is not more versatile the default Update route for Resource be a PATCH method? Why?

natanfelles.github.io

Messages In This Thread

Resource Routes - PUT vs PATCH - by natanfelles - 07-20-2017, 06:15 PM

RE: Resource Routes - PUT vs PATCH - by Narf - 07-21-2017, 01:46 AM

RE: Resource Routes - PUT vs PATCH - by natanfelles - 07-21-2017, 09:37 AM

RE: Resource Routes - PUT vs PATCH - by skunkbad - 07-21-2017, 04:37 PM

RE: Resource Routes - PUT vs PATCH - by natanfelles - 07-22-2017, 09:17 AM

RE: Resource Routes - PUT vs PATCH - by kilishan - 07-22-2017, 08:02 PM

RE: Resource Routes - PUT vs PATCH - by ciadmin - 07-22-2017, 09:11 PM

RE: Resource Routes - PUT vs PATCH - by natanfelles - 07-22-2017, 09:21 PM

RE: Resource Routes - PUT vs PATCH - by ciadmin - 07-22-2017, 10:04 PM

RE: Resource Routes - PUT vs PATCH - by natanfelles - 07-23-2017, 05:46 AM

RE: Resource Routes - PUT vs PATCH - by Narf - 07-24-2017, 12:17 AM

RE: Resource Routes - PUT vs PATCH - by skunkbad - 07-24-2017, 01:50 PM

RE: Resource Routes - PUT vs PATCH - by Narf - 07-25-2017, 12:26 AM