public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "quentusrex at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2099] Support for SRV records in getaddrinfo Date: Sun, 09 Jan 2011 11:08:00 -0000 [thread overview] Message-ID: <bug-2099-131-WmmX7WKAd4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-2099-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=2099 William King <quentusrex at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |quentusrex at gmail dot com --- Comment #5 from William King <quentusrex at gmail dot com> 2011-01-09 11:08:01 UTC --- If: _someserv._tcp.domain has the host name "host2.domain" associated, Then the proper response would be for getaddrinfo() to do a lookup(name to ip) on "host2.domain". Yes, this is more work than usually happens for a getaddrinfo() call, but I think this would be the proper way to handle the srv record support. In file: sysdeps/posix/getaddrinfo.c after the section of code: line 2131: "if (service && service[0])" would be a good place to add the srv record lookup. If we know the service, and we know the protocol, then we should first query for SRV records, and if none are returned, then continue on as the code currently works. But if SRV records are returned, then handle them. Thoughts? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2011-01-09 11:08 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-2099-131@http.sourceware.org/bugzilla/> 2011-01-09 11:08 ` quentusrex at gmail dot com [this message] 2011-01-09 23:10 ` quentusrex at gmail dot com 2012-03-20 14:26 ` binki at gentoo dot org 2012-07-29 22:51 ` psimerda at redhat dot com 2012-11-19 14:52 ` psimerda at redhat dot com 2012-12-18 14:29 ` psimerda at redhat dot com 2012-12-19 23:39 ` bugdal at aerifal dot cx 2014-02-07 2:52 ` [Bug network/2099] " jsm28 at gcc dot gnu.org 2020-12-21 2:45 ` jscott at posteo dot net 2005-12-30 23:26 [Bug libc/2099] New: " fredrik at dolda2000 dot com 2006-01-15 16:28 ` [Bug libc/2099] " aj at suse dot de 2006-01-15 17:15 ` fredrik at dolda2000 dot com 2006-05-03 6:46 ` drepper at redhat dot com 2006-05-06 3:28 ` drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-2099-131-WmmX7WKAd4@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).