|
|
Posted by Jerry Stuckle on 12/17/51 11:55
Mladen Gogala wrote:
> On Sat, 12 Aug 2006 09:34:36 -0400, Jerry Stuckle wrote:
>
>
>>This not not an Apache restriction. It's one of the HTTP protocol, and
>>there isn't anything Apache can do to "fix" it.
>>
>
> I don't know, but I do see less problems with Apache 2.0.54 then with
> Apache 1.0.3x. I haven't quantified anything
>
>
>>And I understand. You're rather go for a "quick fix" than find and fix
>>the real problem.
>
>
> That does fix the real problem: unnecessary painful issue with "headers
> already sent". If all that I want to do is to issue header() function and
> redirect browser onto another page, then I don't really care about the
> "real problem".
>
Nope. The real problem is why you're sending data in the first place.
There may be a valid reason. However, just using ob_start() just hides
the real problem.
>
>>Glad you're not on my team.
>
>
> No need to get personal here, but since you've put it that way, I too am
> glad that I am not on your team.
>
>
Yep, you wouldn't get away with that on my team. Like anything else -
you should have a reason for using ob_start(). And just using it to
hide the fact you've sent out something ahead of time - but have no idea
what you've sent - is not a valid reason.
Another case of a quick fix instead of finding the real problem. Sooner
or later it will come back to bite you.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|