#45195 [Opn->Bgs]: ob_start handler chunk behavior written wrong
| From: | vrana@php.net | Date: | Wed, 05 Nov 2008 16:12:45 +0000 |
| Subject: | #45195 [Opn->Bgs]: ob_start handler chunk behavior written wrong | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-1366@lists.php.net to get a copy of this message | ||
ID: 45195
Updated by: vrana@php.net
Reported By: sv4php at fmethod dot com
-Status: Open
+Status: Bogus
Bug Type: Documentation problem
Operating System: Win
PHP Version: Irrelevant
New Comment:
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same.
Thank you for your interest in PHP.
Duplicate of bug #42660.
Previous Comments:
------------------------------------------------------------------------
[2008-06-06 21:04:30] sv4php at fmethod dot com
Description:
------------
The documentation of ob_start says that if chunk size is specified,
then the handler is called on the first newline in the output.
This did not make sense since what if the output was binary and had no
new lines chunking would not work at all, I tested and found that the
handler instead "snaps" to the first boundary after an echo is
performed.
I.e. each echo operation is atomic, so if I had a chunk size 10 bytes,
and I echo '123456', '123456', '123456', '123456'; then the
handler will
be called with 2 times, with 12 bytes each time, although there are no
newlines in the output.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=45195&edit=1