5) HTTP performance Here, we consider the performance of HTTP, comparing nonpersistent HTTP with persistent HTTP. Suppose the page your browser wants to download is 100 Kbits long, and contains 5 embedded images, each of which is 100 Kbits long. The page and the 5 images are stored on the same server, which has 300 msec roundtrip time (RTT) from your browser. We will abstract the network path between your browser and the Web server as a 100 Mbps link. You can assume that the time it takes to transmit a GET message into the link is zero, but you should account for the time it takes to transmit the base file and the embedded objects into the link. This means that the server-to-client link has both a 150 msec one-way propagation delay, as well as a transmission delay associated with it. In your answers, be sure to account for the time needed to set up a TCP connection (1 RTT).

a) Assuming non-persistent HTTP (and assuming no parallel connections are open between the browser and the server), how long is the response time the time from when the user requests the URL to the time when the page and its embedded images are displayed? Be sure to describe the various components that contribute to this delay. (8 points)

b) Again, assume non-persistent HTTP, but now assume that the browser can open as many parallel TCP connections to the server as it wants. What is the response time in this case? (8 points)

c) Now assume persistent HTTP (HTTP 1.1). What is the response time assuming no pipelining? (8 points)

d) Now assume persistent HTTP with pipelining is used. What is the response time? (8 points)