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
There is no possibility to enforce amount of outstanding demand (requestN) for response streams and channel requests over network - It would be helpful to communicate maximum outstanding requestN in SETUP frame like client_max_request_n - for requests initiated by server, server_max_request_n - for requests initiated by client. Then server may reject setup if max demand assumed by client (server_max_request_n) exceeds it's own. In spec this may be spelled as client and server MUST respect maximum outstanding demand for outgoing streams, and MAY close the connection if incoming stream violates oustanding demand constraint. In rsocket-java this may be implemented with addition of limitRate to outgoing streams, and incoming streams may be safe guarded with lightweight methods compared to streams-transport demand coordination
The text was updated successfully, but these errors were encountered:
There is no possibility to enforce amount of outstanding demand (requestN) for response streams and channel requests over network - It would be helpful to communicate maximum outstanding requestN in SETUP frame like
client_max_request_n
- for requests initiated by server,server_max_request_n
- for requests initiated by client. Then server may reject setup if max demand assumed by client (server_max_request_n) exceeds it's own. In spec this may be spelled asclient and server MUST respect maximum outstanding demand for outgoing streams, and MAY close the connection if incoming stream violates oustanding demand constraint
. In rsocket-java this may be implemented with addition oflimitRate
to outgoing streams, and incoming streams may be safe guarded with lightweight methods compared to streams-transport demand coordinationThe text was updated successfully, but these errors were encountered: