Andi Gutmans wrote:
Can you give a short summary of what the essence of the change is and
how the APIs have changed (Both the ones available to the PHP
developer and to the extension writer?)
To come back to that topic; there are certainly some implications
to think about, some of the top of my head for the PHP developer:
To my understanding the effect of the chunk size never worked
the way like documented, at least not the last few months or
even years. Currently (new code) as soon as the chunk_size
is reached, the output handler will be started and all data
currently available will be passed through it.
The array returned by ob_get_status() changed.
There are some new features not available to the user land
like flushing the whole output handler stack. I'm not sure
if we should provide this functionality.
Same thing goes for the output handler hook; we
might provide user land API for that but if the coder is
going to use an object or resource as handler context
we'll see once a again the destructor chicken and egg
problem on shutdown.
I always found the user land API (function names) a bit weird
but changing it is probably out of question?
Regards,
--
Michael
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
