Skip to content
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

Add option to limit outstanding requests of stream #268

Open
mostroverkhov opened this issue May 20, 2019 · 0 comments
Open

Add option to limit outstanding requests of stream #268

mostroverkhov opened this issue May 20, 2019 · 0 comments

Comments

@mostroverkhov
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant