| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Fwd: Problem with recv syscall on socket when other side closed connection |
| From: | Denis Perchine <dyp@xxxxxxxxxxxx> |
| Date: | Tue, 27 Jun 2000 11:32:11 +0700 |
| Cc: | kuznet@xxxxxxxxxxxxx, ak@xxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200006270418.VAA03406@xxxxxxxxxxxxxxx> |
| References: | <200006261515.TAA22206@xxxxxxxxxxxxx> <0006270852390S.00485@dyp> <200006270418.VAA03406@xxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
> I need to read all data BEFORE reset occurs. The problem is that I > get EPIPE before I get the data recieved before the reset. > > And I am trying to tell you that you are not guarenteed to > get that data, ever. > > Here is one example, if the network between the sql server and > your client reorders the packets such that the reset arrives before > the "reason" data, TCP will not even take the data packets and > will drop them on the floor. > > The sql server should gracefully do a normal close of the socket > if it wishes the client to receive the data with any amount of > certainty. Ough... Sorry... This was a misunderstanding. It does. And I get EPIPE.. For sure it does. Connection is closed using close syscall. -- Sincerely Yours, Denis Perchine ---------------------------------- E-Mail: dyp@xxxxxxxxxxxx HomePage: http://www.perchine.com/dyp/ FidoNet: 2:5000/120.5 ---------------------------------- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Fwd: Problem with recv syscall on socket when other side closed connection, David S. Miller |
|---|---|
| Next by Date: | Re: Fwd: Problem with recv syscall on socket when other side closed connection, kuznet |
| Previous by Thread: | Re: Fwd: Problem with recv syscall on socket when other side closed connection, David S. Miller |
| Next by Thread: | Re: Fwd: Problem with recv syscall on socket when other side closed connection, kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |