You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found out that it's not possible to stream an http/2 request while streaming the response. Besides the http/2 protocol supports it in theory (and some clients/servers also does in other languages).
Note: At the bottom of this message you will find a list of things to beware of.
Context unrelated to the issue
I'm writting a GRPC Client. GRPC uses HTTP/2 to its full potential. For example, for bi-directional streaming, it allows the client to stream messages by writing the request while the server may also respond with many messages streamed in the response.
Here is a schema explaining how it works - numbers are for message order (I hope it makes things clear):
Hello
I found out that it's not possible to stream an http/2 request while streaming the response. Besides the http/2 protocol supports it in theory (and some clients/servers also does in other languages).
Note: At the bottom of this message you will find a list of things to beware of.
Context unrelated to the issue
I'm writting a GRPC Client. GRPC uses HTTP/2 to its full potential. For example, for bi-directional streaming, it allows the client to stream messages by writing the request while the server may also respond with many messages streamed in the response.
Here is a schema explaining how it works - numbers are for message order (I hope it makes things clear):
This is why I have this code - simplified here for issue purpose (click to open):
The actual issue
Basically, I cannot "write" after the streaming of the response started because the request phase is "ResponseBody".
The error is the following (click me)
Fix hints
[Edit] Removing this part as you can see more in #380
Here is a test that may be interesting (it's WIP)
[Edit] Removing this part as you can see more in #380
Special attentions on implementation
The text was updated successfully, but these errors were encountered: