We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Supporting gRPC (tonic) based on the content-type header. I came across "Combining Axum, Hyper, Tonic, and Tower for hybrid web/gRPC apps" which shows the gRPC with Axum but seems cumbersome.
This will enable browser support and code reuse across both HTTP1/1 and gRPC clients.
It would be good to provide native support with maybe a separate crate e.g. axum-grpc.
The text was updated successfully, but these errors were encountered:
Sounds like you're asking for this example https://github.com/tokio-rs/axum/blob/main/examples/rest-grpc-multiplex/src/main.rs. That combines a REST and gRPC service into one and dispatches based on the content-type. All possible thanks to tower::Service.
tower::Service
Actually tonic already uses axum internally for routing. See https://github.com/hyperium/tonic/blob/master/tonic/src/transport/service/router.rs
Sorry, something went wrong.
Thanks. Closing..
No branches or pull requests
Feature Request
Supporting gRPC (tonic) based on the content-type header.
I came across "Combining Axum, Hyper, Tonic, and Tower for hybrid web/gRPC apps" which shows the gRPC with Axum but seems cumbersome.
Motivation
This will enable browser support and code reuse across both HTTP1/1 and gRPC clients.
Proposal
It would be good to provide native support with maybe a separate crate e.g. axum-grpc.
Alternatives
The text was updated successfully, but these errors were encountered: