rpc request: viable to cache with normal http caching

[pkieltyka]

the design of webrpc is to HTTP-POST to /rpc/<serviceName>/<rpcMethod> a structured JSON string to the webrpc server. Great.. but, as the input argument is sent as the request body, can nginx/CloudFlare/other services use that request body to generate a cache-key needed for basic cache-control rules?

the standard way is to use the URI + query string to generate a cache string -- but, right now, the URI/query string would be the same for all requests in webrpc. But certainly some method calls could be cacheable, so let's make sure we can support it as its the easiest first step to scalability. Some ideas how to make these rpc requests cachable..

1. out of the box support? maybe web servers like nginx already support a way to generate a cache-key for a request body?
2. CloudFlare workers? CF rules, and their new workers stuff looks very flexible, we could probably make it work there
3. Add a request mode in webrpc server to take the request as a query string, which would bring us back to normal http request world, and that could be okay but less ideal then option 1 or 2 above

[pkieltyka]

in order to support this, an easy way is to support GET http method and arguments as query params