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

Break TCPConnection's _read_buffer_size into 3 different variables #3187

Merged
merged 1 commit into from
Jun 18, 2019

Conversation

SeanTAllen
Copy link
Member

Prior to this change, _read_buffer_size was used for 3 different
purposes:

  • Sizing the read buffer
  • Controlling how many bytes to read before yielding the CPU
  • Controlling how many bytes to write before yielding the CPU

This commit provides 3 different variables, one for each of the 3
possible usages.

Closes #3186

Prior to this change, _read_buffer_size was used for 3 different
purposes:

- Sizing the read buffer
- Controlling how many bytes to read before yielding the CPU
- Controlling how many bytes to write before yielding the CPU

This commit provides 3 different variables, one for each of the 3
possible usages.

Closes #3186
@SeanTAllen SeanTAllen merged commit 4bdc04a into master Jun 18, 2019
@SeanTAllen SeanTAllen deleted the issue-3186 branch June 18, 2019 21:48
SeanTAllen added a commit that referenced this pull request Jun 18, 2019
patches11 pushed a commit to patches11/ponyc that referenced this pull request Jun 29, 2019
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.

TCPConnection read/write buffer sizes are using the same variable
2 participants