note 16371 rejected from function.ob-start by jimw
| From: | jimw@php.net | Date: | Sat, 27 Oct 2001 21:39:48 +0000 |
| Subject: | note 16371 rejected from function.ob-start by jimw | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-19514@lists.php.net to get a copy of this message | ||
The "Header already sent" error occurs because you have "output" something to
the browser already. This something can be a blank line somewhere in your php script or one of your
include files. The problem is of course, this blank line can be very difficult to find.
I'm actually not interested in removing all the whitespace from my scripts or include files, so
it's even uglier for me :).
I'm interested in the ramifactions of using ob_start() and ob_end_flush() in all scripts that
use sessions. I've been told there is a performance penalty that will show up on high
transaction websites, but so far that is only subjective and not quantified information.
Anyone have any quantifiable arguments against buffering output when using sessions?
Thanks,
-t