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

Consider phasing-out http-json gateway #157

Open
avive opened this issue Sep 29, 2021 · 0 comments
Open

Consider phasing-out http-json gateway #157

avive opened this issue Sep 29, 2021 · 0 comments

Comments

@avive
Copy link
Contributor

avive commented Sep 29, 2021

We should at some point replace the http-json gateway to encourage more clients to use grpc instead of http/json and so a node doesn't need to have the node listen on 2 different ports - one for grpc and one for http-json - reduced surface is always nice.

We should consider adding grpc-web protocol support to the api - this will enable web clients (that can't create an http/2 socket) to communicate with an api endpoint directly and is becoming the standard. There are already easy ways to enable this in Rust (e.g. tonic-web) but I'm not 100% sure about go.

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