On 3/3/2014 08:52, Andrey Repin wrote:
I'd say it again, "sane defaults are better, than alot of options".
Agreed in principle.
However, observe that all network stacks have a bunch of built-in
timeout options. They're rarely exposed to the user level, but their
defaults are typically quite high. (e.g. 60 seconds for connection
timeout.) Over the past 3 decades of TCP/IP, we've discovered that
networks are weird.
for comparison, default DNS _roundtrip_ timeout is 2 seconds,
The typical DNS transaction is just 2 UDP packets, one each direction:
query and response.
I tested a simple, unencrypted LDAP login-and-drop-conn transaction here
against a real production AD server, and it required 8 packets, 5 of
which were TCP/IP connection establishment and shutdown.
Add in the encryption, authentication, and authorization overheads of a
"real" LDAP query, and it could go up to dozens of packets.
That said, it only took about 1 ms to my simple test. The AD server was
on the other side of a router, on a fast WAN.
Someone testing this new cygwin1.dll in a domain environment[*] should
do a packet capture of what Windows sends when the DLL does its new thing.
The captured data isn't terribly interesting here. What we want to know
is how many packets it takes, and what the timestamps are on the
captured frames. Most especially, the delta between the first and last
packets, but if there are any significant time gaps, that could be
interesting, too.
[*] Not me. The only reason we have any AD around here at all is for
testing software that authenticates users against third party AD servers.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
