In that HTTP is all about manipulating a large set of resources (nouns) with a very small set of fixed commands (verbs), and there are no remote procedures at a conceptual level at all.
Right. As I mentioned in a sibling comment, I think I’m using a weaker definition of RPC than what you’re describing here. For me — and I think for most developers in this day and age — RPC is anything which is synchronous and follows request-response semantics. By this definition, all HTTP operations qualify. I understand this is not the original meaning.
In that HTTP is all about manipulating a large set of resources (nouns) with a very small set of fixed commands (verbs), and there are no remote procedures at a conceptual level at all.
score 1 · canonical
Right. As I mentioned in a sibling comment, I think I’m using a weaker definition of RPC than what you’re describing here. For me — and I think for most developers in this day and age — RPC is anything which is synchronous and follows request-response semantics. By this definition, all HTTP operations qualify. I understand this is not the original meaning.
score 2 · canonical
Fair enough. Thanks for the qualification and clarification 👍
score 2 · canonical