This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: TCP stack order question (eCos + 802.11)
- To: "'Grant Edwards'" <grante at visi dot com>,"'Trenton D. Adams'" <tadams at extremeeng dot com>
- Subject: RE: [ECOS] TCP stack order question (eCos + 802.11)
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Mon, 13 Aug 2001 16:30:55 -0600
- Cc: "'eCos Disuss'" <ecos-discuss at sourceware dot cygnus dot com>
Actually, I was just thinking of receiving a maximum of my buffer size,
and then receiving the next bit of data up to the maximum of that buffer
size again until I've got all the buffers. That shouldn't cause a
problem right?
-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of Grant
Edwards
Sent: Monday, August 13, 2001 4:27 PM
To: Trenton D. Adams
Cc: 'eCos Disuss'
Subject: Re: [ECOS] TCP stack order question (eCos + 802.11)
On Mon, Aug 13, 2001 at 04:21:38PM -0600, Trenton D. Adams wrote:
> Doesn't the TCP/IP standard insure that a computer receives
> items in the same order they were sent at the application
> level?
Yes.
> Take for instance if I sent 4 buffers of 200 bytes each. Those
> buffers should arrive on the other end of the TCP connection in
> the same order I sent them as far as the socket programmer is
> concerned right? PLEASE say yes! :)
The bytes arrive in the same order you sent them. They might
not arrive as "4 buffers", and if you depend on that behavior
your software will someday break. ;)
> I'm looking through some RFCs, but I'm not even sure if I'm
> looking at the right ones. Right now I'm looking at
> rfc2126.txt
--
Grant Edwards
grante@visi.com