Comment 1:

I can't make sense of what you're trying to do.  The web server assumes, quite 
reasonably, that when the handler returns, the request is done being handled.  HTTP 
is a synchronous protocol, one request at a time on the wire; there's no other 
possible implementation.
If there are multiple connections then there will be multiple handlers executing in 
parallel and they can do whatever "real time web apps" need to do. 
Leaving open because the documentation should be clearer about the fact that the 
handler returning signals that the request is done.

Labels changed: added documentation.

Owner changed to r...@golang.org.

Status changed to Accepted.

Comment 2 by jesse.dailey:

The real test should be whether, if the Handler doesn't return and doesn't call 
.Close(), but calls Conn.Flush() periodically, does the http.Response return from 
http.Get() immediately after the first flush, and then does Body.Read() keep reading 
all the data (not just data from the first flush).

Comment 3:

@jesse.dailey: yes that works fine, but it's considered bad practice in today's web 
applications.

Comment 4:

This issue was closed by revision 58d5d6f.

Status changed to Fixed.

Merged into issue #-.