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
OkHttpServer does not provide a way to limit the number of max concurrent streams per connection like netty does.
OkHttpClient do handle max concurrent streams setting sent by the server.
OkHttpServerBuilder can provide a way to set max concurrent calls per connection like netty :
…).
* Add option in OkHttpServerBuilder
* Add value as MAX_CONCURRENT_STREAM setting in settings frame sent by the server to the client per connection
* Enforce limit by sending a RST frame with REFUSED_STREAM error
hypnoce
added a commit
to hypnoce/grpc-java
that referenced
this issue
Mar 31, 2024
…).
* Add option in OkHttpServerBuilder
* Add value as MAX_CONCURRENT_STREAM setting in settings frame sent by the server to the client per connection
* Enforce limit by sending a RST frame with REFUSED_STREAM error
hypnoce
added a commit
to hypnoce/grpc-java
that referenced
this issue
Mar 31, 2024
…).
* Add option in OkHttpServerBuilder
* Add value as MAX_CONCURRENT_STREAM setting in settings frame sent by the server to the client per connection
* Enforce limit by sending a RST frame with REFUSED_STREAM error
OkHttpServer does not provide a way to limit the number of max concurrent streams per connection like netty does.
OkHttpClient do handle max concurrent streams setting sent by the server.
OkHttpServerBuilder can provide a way to set max concurrent calls per connection like netty :
grpc-java/netty/src/main/java/io/grpc/netty/NettyServerBuilder.java
Line 404 in 0866e71
Then it has to send this settings to the client per connection and check at every new stream creation (header handling)
The text was updated successfully, but these errors were encountered: