|
|
HTTP/1.1 Explained
Page 2 —
The Nitty
HTTP/1.1's bottom line is saving packets. It allows for larger average packet sizes, more packets per TCP connection, and better use of TCP flow control. That's because 1.1 allows you to buffer output. With HTTP/1.0, the client sends a request to the server. Then the server sends a response back to the client. Then the client sends another request to the server, and the server sends another response to the client. It's kind of like going to a store and asking the clerk for a pack of gum. The clerk gets your pack of gum and gives it to you. Then you ask for a soda. The clerk gets your soda and gives it to you. Then you ask for a magazine. The clerk gets your magazine and brings it back to you. Annoying, isn't it? Well, with 1.1, the client can send as many requests as it wants in succession, and the server can send the responses back in succession as well.
next page»
|
|
|
