From: Tim Hockin <thockin@google.com>
To: musl@lists.openwall.com
Subject: Re: Re: Would love to see reconsideration for domain and search
Date: Sat, 24 Oct 2015 14:33:31 -0700 [thread overview]
Message-ID: <CAO_RewYQWuOUwKVNjX_j_S2-khuP9Z7XRZGcff=XKZXvoBtzeg@mail.gmail.com> (raw)
In-Reply-To: <20151023052625.GD55813@wopr.sciops.net>
[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]
On Oct 24, 2015 12:20 PM, "Kurt H Maier" <khm@sdf.org> wrote:
>
> On Thu, Oct 22, 2015 at 02:24:11PM -0700, Tim Hockin wrote:
> >
> > I understand your point, though the world at large tends to disagree.
>
> The world at large uses bad software. Please don't use this sort of
> reasoning as a justification for and embrace-extend operation on actual
> standards.
Where is the standard that defines ordering semantics in resolv.conf?
> > The real world is not ideal. Not all nameservers are identically
> > scoped - you MUST respect the ordering in resolv.conf - to do
> > otherwise is semantically broken. If implementation simplicity means
> > literally doing queries in serial, then that is what you should do.
>
> You absolutely cannot respect the ordering in resolv.conf; at least not
> if you're relying on someone else's resolver. If the orchestration
> software depends on specific results being returned in particular
> orders, the orchestration software should provide a mechanism to
> generate them.
>
> > Similarly, you can't just search all search domains in parallel and
> > take the first response. The ordering is meaningful.
>
> It should not be, and more to the point will not reliably be,
> meaningful.
Search has to be ordered. You can not possibly argue otherwise?
> You are arguing for introducing performance penalties into musl that do
> not affect you but do very much affect lots of other users. I hope they
> do not happen -- musl is not the right place to fix your problem.
I am arguing for adding a very standard feature (search) to open musl to a
whole new space of users. Nobody is forcing you to use search paths or
ndots.
[-- Attachment #2: Type: text/html, Size: 2083 bytes --]
next prev parent reply other threads:[~2015-10-24 21:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 21:24 Tim Hockin
2015-10-22 21:56 ` Rich Felker
2015-10-22 22:36 ` Tim Hockin
2015-10-22 23:00 ` Josiah Worcester
2015-10-22 23:37 ` Tim Hockin
2015-10-23 4:27 ` Rich Felker
2015-10-23 5:13 ` Tim Hockin
2015-10-23 5:31 ` Rich Felker
2015-10-23 5:37 ` Tim Hockin
2015-10-23 6:00 ` Rich Felker
2015-10-23 6:04 ` Tim Hockin
2016-01-29 0:57 ` Rich Felker
2015-10-27 0:30 ` Rich Felker
2015-10-27 0:37 ` Tim Hockin
2015-10-27 0:45 ` Rich Felker
2015-10-27 8:11 ` u-uy74
2015-11-28 22:48 ` Jan Broer
2015-11-28 23:20 ` Rich Felker
2015-11-29 3:06 ` Jan Broer
2016-01-29 0:58 ` Rich Felker
2015-10-26 2:14 ` Re: Would not " John Levine
2015-10-26 5:14 ` Tim Hockin
2015-10-26 16:16 ` Rich Felker
2015-10-26 17:41 ` John Levine
2015-10-26 18:08 ` Rich Felker
2015-10-23 8:12 ` Re: Would " u-uy74
2015-10-23 9:35 ` Laurent Bercot
2015-10-23 12:23 ` Laurent Bercot
2015-10-23 15:57 ` Tim Hockin
2015-10-23 5:26 ` Kurt H Maier
2015-10-24 21:33 ` Tim Hockin [this message]
2015-10-24 21:57 ` Kurt H Maier
2015-10-24 23:31 ` Rich Felker
2015-10-24 22:02 ` Rich Felker
2015-10-24 22:32 ` Tim Hockin
2015-10-25 8:20 ` u-uy74
2015-10-25 13:06 ` Jan Broer
2015-10-25 13:19 ` u-uy74
2015-10-25 13:39 ` Jan Broer
2015-10-25 14:08 ` u-uy74
2015-10-25 19:08 ` Rich Felker
2015-10-26 1:26 ` Isaac Dunham
2015-10-26 15:35 ` Rich Felker
2015-10-23 15:30 Jan Broer
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='CAO_RewYQWuOUwKVNjX_j_S2-khuP9Z7XRZGcff=XKZXvoBtzeg@mail.gmail.com' \
--to=thockin@google.com \
--cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).