| > But either is important be considered when a user unambiguously specifies | > ai_socktype and/or ai_protocol; to avoid bad/brittle workarounds. | | OK, I added the support. Will be in glibc 2.9. | This is really good news :) | But what about $subject? What is the story with SOCK_DCCP? I added it | now but if it's going away I'd rather remove it. | No, I don't think it will be deprecated, it has been part of several kernel releases in this form already and there was no support in the thread for changing SOCK_DCCP. AS I am guilty of $subject, the story is that the initial suggestion to avoid the trouble with getaddrinfo() by changing the socket type to SOCK_DGRAM, since then presumably an address would be returned. This proved an even poorer workaround than any of the existing ones, in particular since it collides with the (Posix) definition of SOCK_DGRAM, and has been part of kernel releases. Eventually Arnaldo made the most sensible suggestion of why not solving the trouble at the root and update glibc, which is how a message with this subject reached your inbox. This had wider support and I can't think of a better way to solve the problem. Hence many thanks indeed, as the absence of proper DCCP/UDP-Lite support in getaddrinfo() has so far caused quite some grief/frustration. Gerrit -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
