hello, On Sat, 24 Mar 2007, Jun-ichiro itojun Hagino wrote:
| > i understand your concern. current 4-tuple is direct mapping from | > struct sockaddr_in6 (which has those two additional members). | | note however, you must rewrite DNS resolving from gethostby* to | get*info anyways, so i'm not too sure if the number of tuple members in | sockaddr matters that much. This is true when using explicit DNS resolving, but Python socket API allows you to pass in a string in place of the address in the tuple, and then resolves it to an address behind your back. This is probably the most common way of using DNS in Python. It seems that when you have an AF_INET6 socket, it looks for an AAAA record, and when you have an AF_INET socket, it goes for A. Unfortunately this bumps the address family-agnostic get*info API to second place in the convenience-of-use competition (getaddrinfo example at <http://docs.python.org/lib/socket-example.html>). -- erno _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
