Http persistent connection restriction

Clients that use persistent connections SHOULD limit the number of simultaneous
connections that they maintain to a given server. A single-user client SHOULD 
NOT maintain more than 2 connections with any server or proxy.

[..]

I especially doubt that “SHOULD” ... what is this feeling? Why?

I know that persistent HTTP connections, also called HTTP keep-alive, are the idea of ​​using the same TCP connection to send and receive multiple HTTP requests / responses, as opposed to opening a new “request / answer, "I know that using persistent connections is very important to improve HTTP performance.

  • Is there a limit on 2 connections per server or not?
  • When are you requested to use an existing connection or select a new one?

let's say I have an HTML page containing the following image links:

<img src="http://example.com/image1.gif"/>
<img src="http://example.com/image2.gif"/>
<img src="http://example.com/image3.gif"/>
<img src="http://example.com/image4.gif"/>

keep-alive : ? /, , ?

<img src="http://example.com/image1.gif"/>
<img src="http://example.com/image2.gif"/>
<img src="http://example2.com/image3.gif"/>
<img src="http://example2.com/image4.gif"/>

+3
2

"". IE - 2 . ( "" ).

8, ( firefox, safari). IE8 6 .

, 2 . , 2 !

: keep-alive, TCP-, , : .

, TCP , !

HTTP 1.1 , : :

, HTTP- (. ), , , . firefox ( / about: config), Maximum Connections .

: , . . - .

+1

. , image1.gif image2.gif . , image1.gif , image3.gif . .

, , , . , .

- . 50, . , ( ) .

, , .

+2

All Articles