Francois PIETTE wrote:
> however the server obviously didn't call Data.ShutDown(1)
> for some reason?
>>
One reason you could no see the shutdown packet is that the
receiver stopped to receive data and the TCP window is full.
>>
>>> How would that be logged? I've nothing noted l
however the server obviously didn't call Data.ShutDown(1)
for some reason?
One reason you could no see the shutdown packet is that the receiver
stopped to receive data and the TCP window is full.
How would that be logged? I've nothing noted like that.
See attached LanWatch screendump. It s
Francois PIETTE wrote:
>> however the server obviously didn't call Data.ShutDown(1)
>> for some reason?
>
> One reason you could no see the shutdown packet is that the receiver
> stopped to receive data and the TCP window is full.
How would that be logged? I've nothing noted like that.
>
> btw:
Francois PIETTE wrote:
>>> The server can't be sure the file has been sent properly before the
>>> connection is properly closed.
>
>> That's true, however he knows that he sent all, he cannot know
>> whether it all received at the peer.
>
> He knows data is correctly received by the peer because
>> The server can't be sure the file has been sent properly before the
>> connection is properly closed.
> That's true, however he knows that he sent all, he cannot know
> whether it all received at the peer.
He knows data is correctly received by the peer because of the graceful
close sequence