Yes. Output buffering is good. Some people will say that you shouldn't use it, but should make sure to write all your code so that there can't be any output before any headers need to be sent. I disagree with this. While a good idea in principle, in practice it is all but impossible to keep going.
(Or maybe I'm just too lazy to take the tremendous amount of time it would take to rewrite our code to not send output before headers...) Matthew Walker Senior Software Engineer ePliant Marketing -----Original Message----- From: Olexandr Vynnychenko [mailto:[EMAIL PROTECTED]] Sent: Saturday, May 11, 2002 6:35 AM To: [EMAIL PROTECTED] Subject: [PHP] setcookie() in 4.2.0 The following code doesn't work properly on PHP 4.1: <?php echo "<p>Blah, blah</p>"; setcookie("kuku", "abc"); setcookie("lala", "def"); setcookie("zuzu", "ghi"); ?> Because I wrote echo statement before setcookie. But it works on PHP 4.2. Is it due to "output_buffering=4096" directive in php.ini? -- Best regards, Olexandr mailto:[EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
