freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
Re: [freetds] Terminology? new network timeout code
- From: crawford charles <fiducianettestz AT yahoo.com>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Terminology? new network timeout code
- Date: Mon, 8 Jan 2007 08:42:38 -0800 (PST)
Pardon a newbie question:
What form does a NOOP take in TDS? I do not think I have seen a description
anywhere. From the context of your email, I believe know what it is for, and
what it would do, just not what it looks like.
Thanks.
C.
Peter Deacon <peterd AT iea-software.com> wrote: On Sat, 6 Jan 2007, James K.
Lowden wrote:
> On sending the cancel, we may get EAGAIN. We then select(2) until we know
> either 1) it succeeded or 2) it didn't. On failure, close the socket,
> tell the app, and fail the function.
> On success, we read(2) and wait for a reply with select(2). If we get
> one, great. If the client's timeout expires, we tell him, but all we can
> do is wait some more or give up and close the connection. If he tells us
> to cancel again, we wait some more.
> All the while we're waiting, we have a read pending. If the server can
> communicate with us, we might learn he's closed the connection (FIN
> arrives, read returns 0). If the wire's broken, we might never get the
> FIN but eventually read would return <0 and errno would be ETIME. Either
> way, we have to close the connection and mark it DEAD.
You can have a TCP connection open for a year and have absolutely no
data go through it and it would still be concidered a valid, active
connection.
Read does not generate any messages on the network and TCP has no concept
of keepalives so this needs to be handled by TDS. Offhand reads don't
timeout unless you use select.
> So maybe the code isn't so wrong after all.
> You concur?
If it matters and if the code is wrong is really dependant on how the
database servers react. In the case of cancel it might not be such a big
deal to send a handful of cancel messages however in other areas resending
previous commands rather than a NOOP might ruin someones day.
take care,
Peter
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
[freetds] new network timeout code,
James K. Lowden, 01/05/2007
- Re: [freetds] new network timeout code, James K. Lowden, 01/07/2007
- <Possible follow-up(s)>
-
Re: [freetds] new network timeout code,
ZIGLIO, Frediano, VF-IT, 01/05/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/06/2007
-
Re: [freetds] new network timeout code,
Peter Deacon, 01/06/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/06/2007
-
Re: [freetds] new network timeout code,
Peter Deacon, 01/06/2007
- Re: [freetds] Terminology? new network timeout code, crawford charles, 01/08/2007
-
Re: [freetds] new network timeout code,
Peter Deacon, 01/06/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/06/2007
-
Re: [freetds] new network timeout code,
Peter Deacon, 01/06/2007
- Re: [freetds] new network timeout code, James K. Lowden, 01/06/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/06/2007
- Re: [freetds] new network timeout code, ZIGLIO, Frediano, VF-IT, 01/05/2007
-
Re: [freetds] new network timeout code,
ZIGLIO, Frediano, VF-IT, 01/08/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/08/2007
- Re: [freetds] new network timeout code, michael . peppler, 01/09/2007
- Re: [freetds] new network timeout code, James K. Lowden, 01/08/2007
- Re: [freetds] new network timeout code, James K. Lowden, 01/09/2007
-
Re: [freetds] new network timeout code,
James K. Lowden, 01/08/2007
- Re: [freetds] new network timeout code, ZIGLIO, Frediano, VF-IT, 01/08/2007
- Re: [freetds] new network timeout code, ZIGLIO, Frediano, VF-IT, 01/08/2007
- Re: [freetds] new network timeout code, Lowden, James K, 01/08/2007
Archive powered by MHonArc 2.6.24.