Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POST based JSON-RPC support. #12

Open
jmalloc opened this issue Sep 17, 2021 · 1 comment
Open

POST based JSON-RPC support. #12

jmalloc opened this issue Sep 17, 2021 · 1 comment

Comments

@jmalloc
Copy link
Member

jmalloc commented Sep 17, 2021

This is similar to #11, except that it uses a regular POST request instead of a websocket.

  • service-scoped means hitting the /<package>/<service> route, client can invoke any RPC method in that service
  • package-scoped means hitting the /<package> route, client can invoke any RPC method in any service within that package
  • global-scoped means hitting the / route, client can invoke any RPC method available on the server

We could even allow use of non-JSON encodings with JSON-RPC semantics as I think we'd get this for free with existing content type negotation logic. That said, the only reason I can imagine for wanting to use JSON-RPC semantics with native protobuf encoding is to allow batching over HTTP/1.1.

@jmalloc
Copy link
Member Author

jmalloc commented Mar 6, 2022

As with websockets (#35), we will only implement the "global-scoped" behaviour, for simplicity's sake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant