UC知道帮个忙吧！！！E文翻译。。。愁死了。。。
来源：百度知道 编辑：UC知道 时间：2024/05/01 10:14:19
Deliver Policy
In the absence of a Push, a receiving TCP entity is free to deliver data to the user at its own convenience. It may deliver data as each in-order segment is received, or it may buffer data from a number of segments in the receive buffer before delivery.The actual policy will depend on performance considerations. If deliveries are infrequent and large, the user is not receiving data as promptly as may be desirable. On the other hand, if deliveries are frequent and small,there may be unnecessary processing both in TCP and in the user software, as well as an unnecessary number of operating system interrupts.
In the absence of a Push, a receiving TCP entity is free to deliver data to the user at its own convenience. It may deliver data as each in-order segment is received, or it may buffer data from a number of segments in the receive buffer before delivery.The actual policy will depend on performance considerations. If deliveries are infrequent and large, the user is not receiving data as promptly as may be desirable. On the other hand, if deliveries are frequent and small,there may be unnecessary processing both in TCP and in the user software, as well as an unnecessary number of operating system interrupts.
as I can see,this essay is mainly talk about one famous protocol--TCP(translation control protocol)
传输策略：
没有推，TCP在接受到一个个体可由自身自由传送，他甚至可以以他接受到的段（段是专业词汇）的顺序来传送，或者他也能在传送之前对一定量的段进行缓冲。但实际上要考虑实际情况。如果如果传输不频繁也大不频繁也大，用户就不会受到预想中的数据，另一方面，如果传输频繁而且小，那么在用户软件和TCP（协议）就会有不必要的处理，同时还有也不必要的操作系统（CPU）中断
递送政策
缺乏推，一个接受传输控制协议实体免费在它自己的方便递送数据给使用者。 它可能递送数据如每个在-次序片段被收到, 或它可能来自一些片段的缓冲数据在那接受递送前的缓冲。真实的政策将会仰赖表现考虑。 如果递送是稀少的和大, 使用者没有在接受数据当做敏捷地当做可能是令人想要的。 另一方面，如果递送是时常发生的和小,在传输控制协议和使用者软件都可能有不必要的处理, 连同操作系统中断的不必要数字。