in reply to (OT?) Output buffering w/Apache

As I understand it you cant do this. The browser will wait for the EOF when the socket closes before rendering. If you want dynamic content on the browser look at server push protocols. Have a look here for lots of info on dynamic content.

UPDATE Quote:

Server push -- the server sends down a chunk of data; the browser display the data but leaves the connection open; whenever the server wants it sends more data and the browser displays it, leaving the connection open; at some later time the server sends down yet more data and the browser displays it; etc.

Sounds to be very much what you require. HTH
--

Zigster

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

Replies are listed 'Best First'.
Re: Re:(Zigster) (OT?) Output buffering w/Apache
by voyager (Friar) on Apr 10, 2001 at 18:59 UTC
    Ok, what I really was trying to test was browser behavior with a very large document that was a) formatted as one big table, b) not ... so user would begin to see results asap. But since my browser is on same machine as web-server, I was having to send a rediculous amount of data to see any delay, so I thought I'd try and fake it.

    Update: I was pretty sure that partial results could be displayed because I was this:

    Not exactly rocket science, was it? Still, there are some fine points here. One is that the program returns headers and the top portion of the page before asking AOLserver for a database connection or asking the database to do anything. This kind of construction ensures that users aren't staring at a blank Netscape window. here