Nuh 🔻 on Nostr: PUT: a file as is to a given path that you decide, such that the result is always the ...
PUT: a file as is to a given path that you decide, such that the result is always the same no matter how many times you make the request.
Patch: usually append a file with some data, unlike PUT, number of requests matter.
POST: a form or an input, that the backend will handle as it sees fit, and you don't know the URL of the resource that the backend may or may nor create, for example you POST a request to order something, and the backend responds with the ID of the order to keep track of later. obviously the number of times you order something matters.
You can make fun of HTTP semantics, but you will just end up reinventing them in your new RPC, and force people to learn your new semantics because you didn't want to learn the old ones.
Patch: usually append a file with some data, unlike PUT, number of requests matter.
POST: a form or an input, that the backend will handle as it sees fit, and you don't know the URL of the resource that the backend may or may nor create, for example you POST a request to order something, and the backend responds with the ID of the order to keep track of later. obviously the number of times you order something matters.
You can make fun of HTTP semantics, but you will just end up reinventing them in your new RPC, and force people to learn your new semantics because you didn't want to learn the old ones.
quoting note14mx…sg4vPost / Put / Patch = why