The original HTTP protocol used TCP/IP as the underlying network protocol.For each page,graphic,or applet,a separate TCP session was constructed,used,and torn down.Because of the overhead of building and destroying TCP/IP connections,performance problems resulted from this implementation method.Would using UDP rather than TCP be a good alternative? What other changes could you make to improve HTTP performance?
问题信息
-
扫描二维码，关注牛客网
- 意见反馈
-
下载牛客APP，随时随地刷题
扫一扫，把题目装进口袋
- 求职之前，先上牛客
-
扫描二维码，进入QQ群
扫描二维码，关注牛客公众号
- 公司地址：北京市朝阳区北苑路北美国际商务中心K1座一层-北京牛客科技有限公司
- 联系方式：010-60728802 投诉举报电话：010-57596212（朝阳人力社保局）
- 牛客科技© All rights reserved admin@nowcoder.com
- 京ICP备14055008号-4 增值电信业务经营许可证 营业执照 人力资源服务许可证
-
京公网安备
11010502036488号
Despite the connection-less nature of UDP,it is not a serious alternative to TCP for the HTTP.The problem with UDP is that it is unreliable,documents delivered via the web must be delivered reliably.(This is easy to illustrate- a single packet missing from an image downloaded from the web makes the image unreadable.)
One possibility is to modify how TCP connections are used.Rather than setting up-and breaking down- a TCP connection for every web resource,allow persistent connections where a single TCP connection stays open and is used to deliver multiple web resources.