Le 2020-09-29 12:37, Lennart Poettering a écrit :
This is not the reality I live in though. New-style high level
programming languages tend to avoid being just a wrapper around C
APIs. And thus they implement minimal DNS clients themselves, ignoring
the LLMNR, mDNS and so on.
Not just for DNS. For SMTP, HTTP, etc.
The modern way of coding apps is minimal marginally-compliant and secure
built-in network client (so things sort of work on the dev system and in
CI/CD unit tests), with the OS interposing a full-featured protocol
proxy in “production” deployments.
The problem is that this software dev trend conflicts with the
traditional end-to-end IETF view. When the end-to-end view wins you end
up with a single canonical network client like chrome or firefox because
coding a full-featured secure network client implementation is hard and
devs want their apps to do network-like IPC not depend on libs that may
or may not have the correct legal or language requirements
Regards,
--
Nicolas Mailhot
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
