Re: konqueror 3.1 + ipv6

["Todd T. Fries" <todd@fries.net>]

Didn't -current get a commit of a threadsafe getaddrinfo more than a week ago?

Given, other uses of res_* functions are not coming before 3.3, but .. what
we have should at least suffice to presume threadsafeness for getaddrinfo, no?
My testing/application seems to indicate so...
-- 
Todd Fries .. todd@fries.net

I'm available for hire!  http://todd.fries.net/resume.html

(last updated 2003/01/02 02:08:59)

Penned by Marc Espie on Fri, Feb 07, 2003 at 02:13:09PM +0100, we have:
| On Fri, Feb 07, 2003 at 07:00:47AM -0600, Todd T. Fries wrote:
| > As itojun and I discussed, the lookup routines in the kdelibs are quite
| > wrong in their separation of ipv6 and ipv4.  It should be 'transparent'
| > and if necessary allow disabling of one or the other, but for a given
| > name, should try try all addresses, ipv6 and ipv4, for each name, in
| > the order 'all ipv6' ... 'all ipv4' .. which is what our libc does.
| > Unfortunately they think they know better and use c++ to make separate
| > handling of ipv6 and ipv4 ;-(
| The problem is that our getaddrinfo is not thread-safe, and that the
| roll-your-own one in kde is slightly bogus. Choose one evil... either
| non working knode, or bogus IPv6.
| 
| Obviously, no-one cares about IPv6, or we would have a thread-safe
| getaddrinfo since two years ago...