[freetds] Strange TODO
ZIGLIO, Frediano, VF-IT
Frediano.Ziglio at vodafone.com
Fri Jul 25 11:22:30 EDT 2008
> Thus spake Frediano:
> > How to fix all these problems??
> > - we have no safe source for servent_data (private libc
> header is not
> > installed). - we can implement a thread-safe getservbyname locking
> > _servent_mutex directly and call getservbyname_r (not that
> clean) and
> > endservent_r (avoid leaks). - use getaddrinfo, is it
> thread-safe under
> > NetBSD ??
> It turns out we're going about this all wrong. Instead of
> et al., we should be using getnameinfo/getaddrinfo. Those should be
> threadsafe on any platform, and are standard.
> Do you think it's feasible to abandon getservbyname_r? Do we
> support any
> platform on which getservbyname_r is implemented but
> getaddrinfo is not?
Yes, we can do. The problem is that some getaddrinfo implementations (FreeBSD or NetBSD if
I remember) are NOT threadsafe !! But well... perhaps nowadays these platforms are quite
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3129 bytes
Desc: not available
Url : http://lists.ibiblio.org/pipermail/freetds/attachments/20080725/7b9086ff/attachment.bin
More information about the FreeTDS