The request-response sequence looks exactly the same as it does in HTTP/1.0. The only difference is that all communication happens on the same TCP connection instead of a different connection for each request.
Eventually, a Content-Encoding header that allows for document compression will be introduced to the mix. If a client indicates that it can "deflate" content encoding by sending an Accept-Encoding: deflate header in its request, the server will compress the contents of the document (but not the header response) and send it on its way. Jigsaw, a little-known Java-based server, already supports the Content-Encoding header, but popular servers like Apache have yet to implement it.
next page»
