> Btw: can the aplication somehow ask the tcp/ip stack what was > actualy acked? > (ie. how many bytes were acked). No, and you shouldn't want to know. Even if the other end ACKed the data, that doesn't mean that the application on the other end didn't crash. So it won't tell you what you want to know, which is 'did the application on the other end process the data?'. Application-level guarantees can only be provided by application-level code. DS - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: Client receives TCP packets but does... Dan Podeanu
- Re: Client receives TCP packets but... Dan Podeanu
- Re: Client receives TCP packets but... dean gaudet
- Re: Client receives TCP packets but does not ACK Gérard Roudier
- Re: Client receives TCP packets but does not ACK Jan Hudec
- Re: Client receives TCP packets but does not ACK dean gaudet
- Re: Client receives TCP packets but does not... Jonathan Morton
- Re: Client receives TCP packets but does... dean gaudet
- Re: Client receives TCP packets but... Jonathan Morton
- Re: Client receives TCP packets... dean gaudet
- Re: Client receives TCP packets but does not ACK David Schwartz
- Re: Client receives TCP packets but does not ACK Alan Cox
- Re: Client receives TCP packets but does not ACK Andi Kleen
- Re: Client receives TCP packets but does not ACK Nivedita Singhvi