Unix Programming - Re: non-blocking socket close

This is Interesting: Free IT Magazines  
Home > Archive > Unix Programming > May 2007 > Re: non-blocking socket close





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: non-blocking socket close
skaller

2007-05-03, 1:23 pm

On Tue, 01 May 2007 17:12:44 +0000, Andrei Voropaev wrote:

> Is your Firefox running on Windows or on Unix system?


Ubuntu 6.10

> The easiest way to see exactly what's going on is to use the tcpdump or
> ethreal.


I tried to figure out how tcpdump works but couldn't ;(

>Then you'll see if the data is sent and when it is sent. All I
> can say here is that the thing you observe is not the fault of the Linux
> kernel, close on the socket gurantees to deliver all of your data before
> sending FIN. 10 years of network programming confirm this


That's obviously not the case, no such guarrantee is possible.
The client could simply stop reading the data. The kernel HAS to give
up at some stage or the socket resource would exist forever.


--
John Skaller
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com