It was fairly common to use the "trick" (not sure it really was a trick, maybe someone else remembers) where the connection/transaction was kept open. Sites displaying logs, for example, used it as well. As I recall, they used "Transfer-Encoding: chunked", where instead of including a content size, the data consisted of said chunks that were all prefaced with their size, and you could send arbitrarily many.
That way, the browser could parse and display each chunk as it was received. A 0-sized chunk would be the last one, but you did not have to send it.
I don't recall exactly what came first. It's well possible that "chunked" only appeared in HTTP/1.1, but that HTTP/1.0 maybe did not need it since it closed the connection after handling a request anyway, or some such.
Comments
It was fairly common to use the "trick" (not sure it really was a trick, maybe someone else remembers) where the connection/transaction was kept open. Sites displaying logs, for example, used it as well. As I recall, they used "Transfer-Encoding: chunked", where instead of including a content size, the data consisted of said chunks that were all prefaced with their size, and you could send arbitrarily many.
That way, the browser could parse and display each chunk as it was received. A 0-sized chunk would be the last one, but you did not have to send it.
I don't recall exactly what came first. It's well possible that "chunked" only appeared in HTTP/1.1, but that HTTP/1.0 maybe did not need it since it closed the connection after handling a request anyway, or some such.