Am 08.12.2009 um 15:52 schrieb Bret Lambert:
The existing resolver code is compleat balls, as oga@ would spell it. Frankly, it needs to be dragged behind the chemical sheds and quietly suffocated.
Wouldn't it be possible to at least put a lock around it, so that at least it does not produce bogus lookups, but is does sequentiel but correct lookups instead? This would at least not break POSIX and would be compatible to thread-safe implementations, though slower than thread-safe implementations. It would already be a big relieve for programmers if they can just use getaddrinfo and know that they at least get a correct result on any OS. ATM, I have to do a whitelist of operating systems that are known to have thread-safe implementations and do a lock for the others.
-- Jonathan
