-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Remove result/error envelope in streaming RPC response #1254
Comments
You should be able to use |
Sure. let me find some examples and try it. thanks. |
i was reading https://grpc-ecosystem.github.io/grpc-gateway/docs/httpbody.html, can we use it with gRPC stream ? basically i am building download rpc which works as gRPC stream for clients and http byte stream for http clients. |
If it doesn't already work with streaming we should try to make sure it can work. Can you test it? |
i couldn't find examples. Can you point me to right examples ? thanks. |
Doesn't look like we have any, but we have this: https://grpc-ecosystem.github.io/grpc-gateway/docs/httpbody.html |
Seems not working.
gRPC implementation
response
mux is
httpbody.HttpBody type conversion is not ok. hence else block is executed.
|
Okay, lets try and get this in for v2, if you'd like. |
This is fixed in v2 |
grpc-gateway wraps stream response in result/error envelope.
Does result/error envelope required ? nice to have an option to skip result/error envelope ?
Could you help me to understand the reasons behind result/error envelope design ?
in case http byte stream apis (ex: download rpc), this extra envelope is not useful.
The text was updated successfully, but these errors were encountered: