From: Jim Castleberry <cjn@cypress.com> Date: Thu, 28 Nov 2002 18:59:46 -0700 Yes, rfc2525 (Known TCP Implementation Problems) says that when the app closes with unread receive data then you must send a RST. But it doesn't say you have to process the CLOSE immediately. And rfc793 (TCP) says you *shouldn't* process the CLOSE until all preceding SENDs have been dealt with. I totally disagree with your assesment of the RFCs and the Linux logic is not going to change. Furthermore, even if I changed it _today_ and 2.4.21 was released with the changed behavior, every app worth it's salt _MUST_ still deal with the existing behavior so that it runs on kernels deployed all across the universe. So even if it was a 50/50 issue and the choice was arbitrary, the apps still need to be fixed to work on existing kernels (and other OS's which mirror Linux's current behavior). I am not talking about this topic any longer, it comes up once every few months and people get more and more thick headed each time it is discussed. The solution is to fix the buggy server/client. - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
