Posted by Jonathan N. Little on 11/12/05 00:55

Erwin Moller wrote:

> Jonathan N. Little wrote:
>
> <snip a lot>
>
>>>Thanks for your response.
>>
>>Same here, would really like to help.
>>
>
>
> Hi Jonathan,
>
> I the other branch of this thread (Dylan Parry) I describe what I think the
> problem was.
> Dylan's response triggered me into the right direction.
>
> It turn out that IE IS following the hash if I turn output buffering on.
> Simple by adding ob_start() the problem is gone.
>
> I found a few other people on the net who advocate output buffering ON with
> PHP under IIS for different reasons (most concerned a very slow
> userexperience with outputbuffereing off.).
>
> My current workinghypotisis (based on Dylans hunch) is this:
> - If IE gets fragmented data in, it 'forgets' to jump.

Sounds plausible, IE is not the only browser that can get confused when
data comes in dribs and drabs.

>
> My former setup was excactly doing that:
> 1) An URL with a hash
> 2) Building the HTML page bit by bit including a rather long table that
> takes some time to get in (a 2 second query).

What if you presented a temp 'loading' page as you build up the final a
page? Can be done in Perl, should be in PHP too, I'm just new to PHP.

>
> Well, output-buffering is really easy to turn on, and all the problems are
> gone, so I am happy enough now to enter the weekend with a smile. :-)
>
> Thanks for your time and sorry for my rather irritated tone in my last
> response. :-)

No problem-o I full understand how frustrating debugging can be! But you
cannot imagine how many times in the NG there is a call for help with no
code. Some do like to tweak but many want to help.

ob_start() works then call it a week, grab a cold one and forget about
it 'til Monday!


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[Back to original message]