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.

Sign up for GitHub

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

Jump to bottom

can not open stream anymore when the number of stream touch the MaxIncomingStreams #4

Open
glenn-lg opened this issue Mar 27, 2019 · 2 comments
Open

can not open stream anymore when the number of stream touch the MaxIncomingStreams #4

glenn-lg opened this issue Mar 27, 2019 · 2 comments

Comments

@glenn-lg
Copy link
Contributor

What happened:
the quic-go has a limit of incoming streams,using the defaut MaxIncomingStreams(100), we only send less then 100 messages

What you expected to happen:
no message number limit
@qizha
Copy link
Collaborator

qizha commented Mar 27, 2019

you mean the limitation on server side or client side?

@glenn-lg
Copy link
Contributor Author

you mean the limitation on server side or client side?

yes，both server and client have the limitation

swx457056 added a commit to sandhyaravi/viaduct that referenced this issue Apr 25, 2019
@swx457056
Merge pull request kubeedge#4 from srivatsav123/patch-3
8244de0 
Update README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@qizha @glenn-lg