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 optional $writeChunkSize parameter for max number of bytes to write #105

Merged
merged 1 commit into from
May 19, 2017

Conversation

clue
Copy link
Member

@clue clue commented May 19, 2017

This complements the $readChunkSize that is available for the readable side of streams.

Among others, this can be used to work-around the TLS stream write issues for chunks larger than ~30KB mentioned in #64.

@clue clue added this to the v0.7.1 milestone May 19, 2017
@WyriHaximus WyriHaximus requested review from jsor and WyriHaximus May 19, 2017 17:31
@clue
Copy link
Member Author

clue commented May 19, 2017

Unrelated HHVM test failure is being addressed via #106 :shipit:

@kelunik
Copy link

kelunik commented May 19, 2017

Are you sure that works around the issue?

@clue
Copy link
Member Author

clue commented May 19, 2017

Are you sure that works around the issue?

This PR is merely a new feature for the stream component :-) Among others, this can be used to work around the issue mentioned in #105, which actually happens in the socket component. I do not think that this "fixes" the issue, but we've seen cases where this can be used to work around this issue and we have yet to spot any issues with this work around. This seems to suggest it's well worth a try 👍 That being said, we strongly encourage people to update PHP to the latest versions, which will ultimately fix this issue altogether 👍

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

Successfully merging this pull request may close these issues.

4 participants