[PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread MikeB
chris h wrote: I'm working through my class on PHP and I tried to put information from my sign-on process in the navbar. This didn't work well, since I had to reload the page to see it as the navbar was constructed earlier in the code than the signon process. (Hard to explain, as we are

Re: [PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread Richard Quadling
On 14 October 2010 15:01, MikeB mpbr...@gmail.com wrote: chris h wrote: I'm working through my class on PHP and I tried to put information from my sign-on process in the navbar. This didn't work well, since I had to reload the page to see it as the navbar was constructed earlier in the

Re: [PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread Richard Quadling
On 14 October 2010 15:09, Richard Quadling rquadl...@gmail.com wrote: then that is _PROBABLY_ of for a small one of script or a very very ... _PROBABLY_ ok ... -- Richard Quadling Twitter : EE : Zend @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY -- PHP General Mailing List

Re: [PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread Peter Lind
Just out of curiosity: why were you told to switch off output buffering? Regards Peter -- hype WWW: plphp.dk / plind.dk LinkedIn: plind BeWelcome/Couchsurfing: Fake51 Twitter: kafe15 /hype -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread MikeB
Peter Lind wrote: Just out of curiosity: why were you told to switch off output buffering? Regards Peter I can't find the thread now, but it was in regards to my early experiments with cookies. I was creating cookies and it worked mid-code, since buffering was active. Then someone said

Re: [PHP] Re: Buffering output to allow headers late in code?

2010-10-14 Thread chris h
Then someone said that using buffering was a bad idea and I should disable it. I think it leads to poor habits like calling controller methods out of the view (essentially what you are wanting to use it for). Using it like that is asking for spaghetti code that's hard to maintain, scale, and