I asked Andrew something to the effect of “What promises does TCP make about when it will get around to writing data to the network?
Not many promises, but some. I’ll try and quote chapter and verse on this: References: RFC 1122, “Requirements for Internet Hosts” (also STD 3) RFC 793, “Transmission Control Protocol” (also STD 7) • The socket interface does not provide access to the TCP PUSH flag. • RFC1122 says (4.2.2.2): A TCP MAY implement PUSH flags on SEND calls. If PUSH flags are not implemented, then the sending TCP: (1) must not buffer data indefinitely, and (2) MUST set the PSH bit in the last buffered segment (i.e., when there is no more queued data to be sent). • RFC793 says (2.8): When a receiving TCP sees the PUSH flag, it must not wait for more data from the sending TCP before passing the data to the receiving process. [RFC1122 supports this statement.] • Therefore, data passed to a write() call must be delivered to the peer within a finite time, unless prevented by protocol considerations. • There are (according to a post from Stevens quoted in the FAQ [earlier in this answer – Vic]) about 11 tests mad
Related Questions
- Ive installed CAMEO on a network and am concerned about file and data security in a multi-user setting. Can I lock any of CAMEOs files or directories to protect them?
- I asked Andrew something to the effect of "What promises does TCP make about when it will get around to writing data to the network?
- Can a voice/data IP network be as reliable as traditional circuit-switched voice networks?
