Clarify ob_get_status buffer_size and ob_start chunk_size behavior#5260
Open
lacatoire wants to merge 1 commit intophp:masterfrom
Open
Clarify ob_get_status buffer_size and ob_start chunk_size behavior#5260lacatoire wants to merge 1 commit intophp:masterfrom
lacatoire wants to merge 1 commit intophp:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
buffer_sizeinob_get_status(): explain it is the currently allocated buffersize (not the amount of data), grows dynamically, and is aligned to memory page boundaries
(minimum 4096 bytes)
chunk_size = 1behavior inob_start(): the buffer is flushed after every outputoperation, effectively disabling buffering
Fixes #3816