>> I don't recall it being discussed before. Of course, if you set up a >> caching-only name server right on the machine that runs htdig, the >> nameserver requests would likely become a non-issue. That's probably >> a cleaner solution than putting caching right into htdig, although it >> might be easy enough to add an IP address field to the Server class and >> have htdig use that for connections.
Alright. On a semi-related note, is there work being done to keep a TCP connection to a particular server alive for multiple requests? _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
