Re: ADO ConnectionTimeout taking 2.3s rather than 1.0s

Ian Boyd wrote:
i am starting the clock just before i call Connection.Open.

Then you are not truly timing the ConnectionTimeout: you are timing
the amount of time it takes for the Connection to acquire a "handle"
to the database server plus the time it takes the ConnectionTimeout
to time out. Again, there is no control over the first part.

Then i guess my question is why do ADO guys implement it so poorly?
01
Yes, it does seem trivial doesn't it. I suspect it's due to an inability to
cancel the request to the network services, but that is pure speculation,
and maybe totally offbase. Maybe it's trivial to cancel that call, or allow
it to die on its own. Perhaps they had another reason for implementing it
this way ... I'm not privy to their reaoning on this and, unfortunately,
it's a little late in the day to be requesting any changes to ADO. :-(

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"


.