I get the reluctance but I still think it’s somewhat semantic from the server’s perspective:
HTTP verbs are cache controls, which is not unusual for RPCs (otherwise would be done in request metadata/headers/etc)-- middleboxes are generally aligned with this.
HTTP endpoints (or “resources”) are encoded procedure names
To me, HTTP is a somewhat specialized kind of RPC (with specified caching and method encoding). We can of course build other kinds of RPCs on top of any RPC too.
We can draw the line elsewhere, but at the very least HTTP is very close to being an RPC. :)
I get the reluctance but I still think it’s somewhat semantic from the server’s perspective:
To me, HTTP is a somewhat specialized kind of RPC (with specified caching and method encoding). We can of course build other kinds of RPCs on top of any RPC too.
We can draw the line elsewhere, but at the very least HTTP is very close to being an RPC. :)
score 2 · canonical