[Common-dev] Where should the internal resolver go?
Tom Marshall tmarshall at helixcommunity.orgI'm working on updating the "internal resolver" for IPv6. This is a stub resolver implemented entirely in Helix code. It uses a UDP socket to send and receive queries. It parses the results and does caching. This method has both advantages and drawbacks: - It is fully nonblocking without requiring any new threads. - It ensures that answers are cached, which can reduce the network load and improve response time. - It only does DNS. It cannot lookup other types of names (eg. NETBIOS). The internal resolver has been exclusive to the Unix server/proxy until now. But it is perfectly capable of running on the client and on Windows. So I would like to know if there is any interest in using this code in other products besides the server/proxy. If so, I can put it in the common/netio tree so that it can be conditionally included with various product builds. -- Real Users never know what they want, but they always know when your program doesn't deliver it. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.helixcommunity.org/pipermail/common-dev/attachments/20040527/17d2e768/attachment.bin