Support JSON-RPCv2

[stevenroose]

The tagline of the project says gRPC to JSON proxy. However, "JSON" is just a data format. Somehow a RESTful service is created instead of using an existing JSON-based RPC protocol, i.e. JSON-RPC (v2).

What is the motivation of this decision? Why not support JSON-RPC instead of REST?

[AlekSi]

That would be a totally different project.

[stevenroose]

@AlekSi I realize that. Just curious why REST was chosen? REST (being resource-centric) and RPC are fundamentally different. JSON-RPC defines a JSON & HTTP-based RPC protocol, why wasn't it picked over REST?

[achew22]

The decision was to implement the gRPC http spec which is a standard part of gRPC implemented by several projects in the same way (Envoy, grpc-httpjson-transcoding, grpc-jersey, and in the paid product side Cloud Endpoints for gRPC APIs). Deviating from the standard would make us incompatible with a wide swath of the gRPC ecosystem.

[achew22]

I'm going to close this since it seems to be stuck. If you have any more issues, please reopen/make a new one.