Do HTTP streaming's TCP receive buffer and client application buffer match? How do they engage without talking?

Match left-column statements to right-column architectures. Always-on server. Processes may provide or receive service. Any communication has a client and server. It's HTTP. User-controlled hosts may be up or down. Self-scalable. A. Peer-to-peer. B. Not client-server or peer-to-peer. C. Client-server/peer-to-peer. D. Client-server. E. TCP/IP.

A common criticism of layered protocols is the apparent overhead of copying at each stage. Is there any way to put a stop to copycats?

Match left-column statements to right-column architectures. Always-on server. Processes may provide or receive service. Any communication has a client and server. It's HTTP. User-controlled hosts may be up or down. Self-scalable. A. Peer-to-peer. B. Not client-server or peer-to-peer. C. Client-server/peer-to-peer. D. Client-server. E. TCP/IP.

Computer A uses the Go-back-N ARQ protocol to send a 110 Mbytes file to computer B with a window size of 15. Given each frame carries 100K bytes data. How long does it take to send the whole file (the total time taken from A sending the first bit of the file until A receiving the last acknowledgment)? Given that the transmission rate of the link is 500 Mbps and the propagation time between A and B is 15ms. Assume no data or control frame is lost or damaged and ignore the overhead due to header and trailer.