TCP has the concept of a session. So block B will definitely be delivered down a
socket after block A.
The only think likely to confuse the receiving program is the fact that the receiving
socket may get it in peculiar lumps.
As long as the receiving program buffers it up till it has a full 'record' there
should be no problems.
-----Original Message-----
From: Nic Wise [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, July 13, 1999 3:02 PM
To: Multiple recipients of list delphi
Subject: Re: [DUG]: TCP/IP Question
Define packets. If you mean:
send block A (which might be 16K, for all I know)
send block B
they _could_ come in as B then A
BUT, TCP/IP will make sure that all of A - if its 16K, it gets split up
into MTU-sized blocks (512 or 1024bytes or whatever its set to) - is in
the right order.
N
Peter Harrison IT wrote:
>
> I am writing a TCP/IP Server.
>
> I am using WinSock.
>
> The client transmits several packets, and I was expecting the packets to
> arrive on the server in the same order. They don't appear to be arriving in
> the same order they left - which is what I thought TCP/IP gives you.
>
> Am I mistaken (and there is a bug in my program), or does TCP/IP not
> actually enforce the order of arrival of packets?
>
> Peter Harrison
> Software Developer
> Sovereign
>
> ---------------------------------------------------------------------------
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
application/ms-tnef
