Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22030
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: <Jared.Williams1@ntlworld.com>
To: "'Michael Wallner'" <mike@php.net>,
	<internals@lists.php.net>
Date: Mon, 27 Feb 2006 12:49:29 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <68.AB.30574.5C7E2044@pb1.pair.com>
Thread-Index: AcY7l/HUMgjVGLb2SVSd8W9OrjFfMgAA7J9A
Message-ID: <20060227124709.TCMT22495.aamta10-winn.ispmail.ntl.com@win2ks>
Subject: RE: [PHP-DEV] Revisiting output control code
From: jared.williams1@ntlworld.com ("Jared Williams")
References: <68.AB.30574.5C7E2044@pb1.pair.com>


> I'd like to suggest that we revisit the output control 
> (output buffering) code base.
> The current implementation uses way too less commands to do 
> too many different operations, which almost always causes 
> problems with output handlers that need to maintain a state 
> or context.
> 
> Short example:
> ob_clean() causes havoc with ext/zlib ob handlers and any 
> handlers found in pecl/http.
> ob_clean() passes currently buffered input through the 
> handler and discards it, which means in the case of the gz 
> handler that the gzip/zlib header bytes (and more) are 
> missing from the sent data.
> 
> Things I think that should come with the new code:
> 	Support for an opaque handler context, which will be 
> passed to the handler.
> 	More distinct commands like FLUSH, RESTART and/or CLEAN.
> Thoughts/comments/flames?

Sounds like should be built upon/replaced with streams.

Jared