I have a question to the web hosting companies reading this.
For your clients, do you have output_buffering set to "on" by default?
If no, why not? Is it very resource intensive?
I recently started coding a users system class, but I would like to know the answer to the above question, as it will have an impact on how I will be coding the class, unless that would be a bad thing?
I am still new in the big world of web development, hence the reason for the maybe obvious question.
Any feedback about output buffing (why on/why off) is appreciated!
; Output buffering is a mechanism for controlling how much output data
; (excluding headers and cookies) PHP should keep internally before pushing that
; data to the client. If your application's output exceeds this setting, PHP
; will send that data in chunks of roughly the size you specify.
; Turning on this setting and managing its maximum buffer size can yield some
; interesting side-effects depending on your application and web server.
; You may be able to send headers and cookies after you've already sent output
; through print or echo. You also may see performance benefits if your server is
; emitting less packets due to buffered output versus PHP streaming the output
; as it gets it. On production servers, 4096 bytes is a good setting for performance
; Note: Output buffering can also be controlled via Output Buffering Control
; Possible Values:
; On = Enabled and buffer is unlimited. (Use with caution)
; Off = Disabled
; Integer = Enables the buffer and sets its maximum size in bytes.
; Note: This directive is hardcoded to Off for the CLI SAPI
; Default Value: Off
; Development Value: 4096
; Production Value: 4096
output_buffering = ____