Hi all- Is there really a difference between ob_gzhandler and zlib.output_compression, now that ob_gzhandler supports chunks? Since, in zlib.c, zlib.output_compression still causes output buffering to be turned on, I can't see that there's a convincing reason to use one over the other, unless you need fine control over the flush/clean functions. Can anyone shed some light on this? Slightly OT: with such an amazing option so easy to implement on top of an existing application (via either PHP or mod_gzip), and widespread browser support, why don't more sites use this? Bandwidth is expensive. CPU cycles are not. We've seen 900K HTML reports compressed to 40K. Truly awesome. Thanks John -- John Donagher Application Engineer, Intacct Corp. Public key available off http://www.keyserver.net Key fingerprint = 4024 DF50 56EE 19A3 258A D628 22DE AD56 EEBE 8DDD -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
