From: Jan Hudec <bulb@ucw.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: Client receives TCP packets but does not ACK
Date: Mon, 18 Jun 2001 13:50:18 +0200 [thread overview]
Message-ID: <20010618135018.A12320@artax.karlin.mff.cuni.cz> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F1477@ftrs1.intranet.ftr.nl>
In-Reply-To: <27525795B28BD311B28D00500481B7601F1477@ftrs1.intranet.ftr.nl>; from f.v.heusden@ftr.nl on Fri, Jun 15, 2001 at 02:53:59PM +0200
> > TCP is NOT a guaranteed protocol -- you can't just blast data from one
> port
> > to another and expect it to work.
>
> Isn't it? Are you really sure about that? I thought UDP was the
> not-guaranteed-one and TCP was the one guaranting that all data reaches the
> other end in order and all. Please enlighten me.
It's "hlaf guaranteed." It guarantees, that if data are delivered to the
reciever, all data sent before already arived and in correct order. But it's
not guaranteed that data succesuly writen on 1 end actualy arived unless the
connection was correctly shutdown and closed.
Btw: can the aplication somehow ask the tcp/ip stack what was actualy acked?
(ie. how many bytes were acked).
--------------------------------------------------------------------------------
- Jan Hudec `Bulb' <bulb@ucw.cz>
next prev parent reply other threads:[~2001-06-18 11:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 12:53 Client receives TCP packets but does not ACK Heusden, Folkert van
2001-06-15 18:27 ` Mike Black
2001-06-15 18:39 ` Gérard Roudier
2001-06-15 19:12 ` Alan Cox
2001-06-17 18:17 ` Pavel Machek
2001-06-17 19:32 ` Alan Cox
2001-06-17 19:40 ` Dan Podeanu
[not found] ` <200106172113.f5HLDhJ377473@saturn.cs.uml.edu>
2001-06-17 22:09 ` Dan Podeanu
2001-06-17 22:35 ` dean gaudet
2001-06-18 11:50 ` Jan Hudec [this message]
2001-06-18 16:17 ` dean gaudet
2001-06-18 16:48 ` Jonathan Morton
2001-06-18 22:30 ` dean gaudet
2001-06-18 23:43 ` Jonathan Morton
2001-06-19 2:46 ` dean gaudet
2001-06-20 21:01 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2001-07-01 21:27 Nivedita Singhvi
2001-07-11 3:43 ` Robert Kleemann
[not found] <E15BiHy-0002xC-00@the-village.bc.nu.suse.lists.linux.kernel>
2001-06-17 20:21 ` Andi Kleen
[not found] <Pine.LNX.4.33.0106121720310.1152-100000@localhost.localdomain.suse.lists.linux.kernel>
2001-06-13 8:48 ` Andi Kleen
2001-06-13 16:09 ` Robert Kleemann
2001-06-13 0:26 Robert Kleemann
2001-06-15 3:50 ` Robert Kleemann
2001-06-15 12:44 ` Mike Black
2001-06-15 18:29 ` Albert D. Cahalan
2001-06-15 23:10 ` Robert Kleemann
2001-06-16 11:55 ` Mike Black
2001-06-16 23:56 ` Robert Kleemann
2001-06-27 1:04 ` Robert Kleemann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010618135018.A12320@artax.karlin.mff.cuni.cz \
--to=bulb@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).