public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "psimerda at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/14965] New: remove AI_ADDRCONFIG from getaddrinfo() flags
Date: Sun, 16 Dec 2012 15:45:00 -0000	[thread overview]
Message-ID: <bug-14965-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=14965

             Bug #: 14965
           Summary: remove AI_ADDRCONFIG from getaddrinfo() flags
           Product: glibc
           Version: 2.15
            Status: NEW
          Severity: normal
          Priority: P2
         Component: network
        AssignedTo: unassigned@sourceware.org
        ReportedBy: psimerda@redhat.com
    Classification: Unclassified


AI_ADDRCONFIG can be beneficial to applications when it's only used for the
connect(), sendto(), etc. See a detailed description of this topic:

https://fedoraproject.org/wiki/Networking/NameResolution/ADDRCONFIG

The defaults are only used when an application doesn't supply hints. But,
virtually any application that wants to connect() wants to also specify at
least the transport protocol (TCP, UDP). That means that applications that
would benefit from AI_ADDRCONFIG won't use the defaults anyway.

-- 
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.


             reply	other threads:[~2012-12-16 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-16 15:45 psimerda at redhat dot com [this message]
2012-12-18 14:25 ` [Bug network/14965] remove AI_ADDRCONFIG from default " psimerda at redhat dot com
2013-01-03 14:54 ` psimerda at redhat dot com
2013-02-24 22:12 ` psimerda at redhat dot com
2014-06-14  5:34 ` fweimer 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-14965-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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: link
Be 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).