On 04/26/2018 04:01 PM, Simon McVittie wrote:
On Thu, 26 Apr 2018 at 11:03:55 +0200, Pavel Šimerda wrote:
It looks easy but in practice it proves by no means trivial to have a proper
IPv4/IPv6 client behavior implemented. I have done many experiments with
that and the situation in open source (or any other) software including the
core components is not satisfactory at all.
If you have a plan for improving the situation, please open bugs or
feature requests on the relevant upstream projects (glibc, Avahi and/or
nss-mdns).
I do not have any motivation to start bug reports or feature request
with abandonware (Avahi and mdns). Also don't you think I have started
enough bug reports with glibc that never get processed simply because
noone is willing to actively work on the resolver code not to say review
proposals that go deep into the API details?
Did I not prove enough knowledge of the topic to avoid template advice?
A short answer that you aren't interested would save us another message
exchange.
Distro maintainers' priority is to avoid introducing regressions for
existing software. I don't intend to make downstream changes in nss-mdns
that cause it to regress for existing software, even if that existing
software is not implemented in the ideal way.
I don't think we want to get into that sort of discussion as part of a
bug report.
I'm convinced that the way to go is to always connect in ~100 ms if there is
either IPv4 or IPv6 available to connect (i.e. do not enforce protocol
precedence when one of the protocol is slower than that)
Of course, but nss-mdns does not control application behaviour. If an
existing application correctly asks for AF_UNSPEC, great; but if it
wrongly resolves one protocol and then the other, nss-mdns is not in a
position to fix that.
That is exactly why I focused on application behavior first and library
behavior only as a second step.
I would be honored if you contacted me directly and we could chat a little
bit rather than have an online e-mail discussion.
Sorry, I do not have enough time available for nss-mdns maintenance to
spend it on private real-time conversations.
Good to know. Let me know at any time if the situation changes or if
there's someone interested. But for now I suppose this discussion is
over. Nice to meet you!
Cheers,
Pavel
