Re: (OT?) Output buffering w/Apache

The trouble I suspect is not in Apache buffering the output but in the web browsers loading of the output. I suspect for an <HTML> tagged document the browser does not display the contents "as it arrives" but instead holds onto everything until the document is finished being sent and then renders the page. The reason for this would be if the browser tried to render the page as it received data - I believe it would make web designing hazardous to your health. That's my guess and AFAIK when sending a document as text/html with <(/)html> tags surrounding you cannot "turn the buffering off"

-Adam Stanley
Nethosters, Inc.

Comment on Re: (OT?) Output buffering w/Apache

Replies are listed 'Best First'.
Re: Re: (OT?) Output buffering w/Apache by sierrathedog04 (Hermit) on Apr 10, 2001 at 19:40 UTC
The major web browsers render pages as they receive data. Update: For instance, visit a fairly long listing of books at http://sailor.gutenberg.org/by-title.html Wait until something displays, and then immediately hit the STOP button. (A better example because it takes longer to download is the full text of Jane Austen's Pride and Prejudice.) If you then scroll to the bottom of your page and you had hit STOP fast enough you will see that the displayed text breaks off abruptly. That is because the browser (IE5.5/Win98 in my case) rendered the page before it had finished downloading the page.	[reply]

Replies are listed 'Best First'.

Re: Re: (OT?) Output buffering w/Apache
by sierrathedog04 (Hermit) on Apr 10, 2001 at 19:40 UTC

Update: For instance, visit a fairly long listing of books at http://sailor.gutenberg.org/by-title.html Wait until something displays, and then immediately hit the STOP button. (A better example because it takes longer to download is the full text of Jane Austen's Pride and Prejudice.)

If you then scroll to the bottom of your page and you had hit STOP fast enough you will see that the displayed text breaks off abruptly. That is because the browser (IE5.5/Win98 in my case) rendered the page before it had finished downloading the page.

[reply]