Re: Output buffering
| From: | David Otton | Date: | Wed, 07 Oct 2009 10:51:10 +0000 |
| Subject: | Re: Output buffering | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-298744@lists.php.net to get a copy of this message | ||
2009/10/7 Arno Kuhl <akuhl@telkomsa.net>:
> Thanks David. After taking another look at the description for ob_start() I
> began to suspect there was a difference, but the manual doesn't mention
> anything about it. And the fact they use the same terminolgy for both the
> settings and the functions is confusing. I can see from tests that the
> htaccess/ini settings have no obvious effect on the ob functions (maybe
> buffer size?).
My understanding (and it's not 100% clear in the manual) is that the
output buffering directive is overloaded - it can be used for both
turning output buffering on and setting the size of the output buffer.
Quote:
; Output buffering allows you to send header lines (including cookies) even
; after you send body content, at the price of slowing PHP's output layer a
; bit. You can enable output buffering during runtime by calling the output
; buffering functions. You can also enable output buffering for all files by
; setting this directive to On. If you wish to limit the size of the buffer
; to a certain size - you can use a maximum number of bytes instead of 'On', as
; a value for this directive (e.g., output_buffering=4096).
output_buffering = 4096