David M. Lloyd wrote: > On Fri, 4 Jan 2008 17:38:23 +0100 > "Maarten Bosteels" <[EMAIL PROTECTED]> wrote: > >> Have you had a look at >> http://mina.apache.org/tutorial-on-protocolcodecfilter-for-mina-2x.html >> ? > > A minor issue with the article - the fragmentation link in the first > section ("Why use a ProtocolCodecFilter?") is completely irrelevant to > how reads and writes are done. IP fragmentation has *no effect* on the > reads and writes - one sent IP packet on the sending side equals zero > or one IP packets on the receiving side, regardless of how it is > fragmented along the way.
If you consider packet lost, SACK and congestion control, there is no grantee these "frame"s would keep intact. some simple case: 1. consider RWIN < "frame" size. 2. consider a slow reader on receiver side.. All of these are handled transparently at the OS (or maybe even a TCP Offload engine). There are no way to get these info in a platform independent way. Never mention there are tons of non-standard TCP congestion control algorithm that interact wildly with QoS routers. TCP is intended to be used as stream, not "frame"s ... > Probably a better link to reference here is "Nagle's Algorithm" [1]. > - DML > > [1] http://en.wikipedia.org/wiki/Nagle%27s_algorithm > -- This space was intended to be left blank.
