These two reasons are in fact of little impact. The real problem I have with output buffering in my web app is that it doesn't handle .xls and .pdf files generated on the fly with PHP. Every time the browser is going to download those kind of files it will get corrupted.
The only solution I could find for this was to disable output buffering. Another thing: you can even compress the buffer before sending it so it will help a lot if a user have little bandwidth. Text files have a very good compression ratio. Cheers, -William On Tue, 2007-06-26 at 09:04 -0400, Robert Cummings wrote: > On Tue, 2007-06-26 at 14:33 +0200, Emil Edeholt wrote: > > Hi! > > > > My php project would get a much cleaner code if I could set cookies > > anywhere in the code. So I thought of output buffering. But I can't find > > any articles on the cons of output buffering. I mean it most be a reason > > for it being off by default? > > Cons of output buffering: > > - teeeeeeeency weency time overhead > - memory overhead since buffered content remains in memory > until flushed. > > Cheers, > Rob. > -- > .------------------------------------------------------------. > | InterJinn Application Framework - http://www.interjinn.com | > :------------------------------------------------------------: > | An application and templating framework for PHP. Boasting | > | a powerful, scalable system for accessing system services | > | such as forms, properties, sessions, and caches. InterJinn | > | also provides an extremely flexible architecture for | > | creating re-usable components quickly and easily. | > `------------------------------------------------------------' > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
