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

Connection buffer configuration #180

Closed

Conversation

olme04
Copy link
Contributor

@olme04 olme04 commented Jul 15, 2021

NOTE: Depends on #178

  • allow to configure connection buffer for sending frames
  • make it default to 64 for now (instead of current unlimited)

@olme04 olme04 force-pushed the connection-buffer-configuration branch from e620d2e to 15b7250 Compare July 15, 2021 14:52
@olme04
Copy link
Contributor Author

olme04 commented Jul 16, 2021

blocked by Kotlin/kotlinx.coroutines#2826

@olme04 olme04 force-pushed the connection-buffer-configuration branch from 15b7250 to a6f2872 Compare July 21, 2021 09:57
@olme04 olme04 force-pushed the connection-buffer-configuration branch from a6f2872 to c32e1ef Compare August 19, 2021 12:37
make it default to 64 for now (instead of current unlimited)
@olme04 olme04 force-pushed the connection-buffer-configuration branch from c32e1ef to e6e9293 Compare August 19, 2021 14:39
@olme04
Copy link
Contributor Author

olme04 commented Dec 12, 2021

After support of transports like QUIC, this change will be different, so PR isn't relevant

@olme04 olme04 closed this Dec 12, 2021
@olme04 olme04 deleted the connection-buffer-configuration branch December 20, 2021 14:44
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

Successfully merging this pull request may close these issues.

None yet

2 participants