Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33447
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain spikesource.com from 209.10.209.56 cause and error)
Reply-To: enugroho@spikesource.com
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain
Organization: Spikesource, Inc.
Date: Mon, 26 Nov 2007 16:47:22 -0800
Message-ID: <1196124442.21880.15.camel@ganges.spikesource.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Reliable header sending mechanism in php 6
From: enugroho@spikesource.com (Ezra Nugroho)

Php Developers,


Can I ask for the following support, at least to begin conversation
about it if it hasn't been done before.

Currently, the header() function still carries the following warning in
its online documentation:

"Remember that header() must be called before any actual output is sent,
either by normal HTML tags, blank lines in a file, or from PHP. It is a
very common error to read code with include(), or require(), functions,
or another file access function, and have spaces or empty lines that are
output before header() is called. The same problem exists when using a
single PHP/HTML file."

This is quite annoying since this makes header() or setcookie() calls to
be unreliable. 

I am aware that it can be done more reliably by turning the output
buffering on. This is less of an issue if you are writing your own
webapp. However, this is much more difficult if a person writes a
library for other people's consumptions. The library cannot enforce
output buffering in the webapp.

Can we please give it a thought in PHP 6? Maybe by turning output
buffering on by default, or even by enforcing output buffering.

In Java, you can get the request object, and the response object of a
web request. I find this very useful and reliable.

Any thoughts or comments about this?


Thank you,
Ezra