Confirmed users
613
edits
Networking/Archive/Necko/DNS/ResolverIntegration: Difference between revisions
Networking/Archive/Necko/DNS/ResolverIntegration (view source)
Revision as of 21:53, 7 August 2013
, 7 August 2013→Summary
| Line 8: | Line 8: | ||
* Steve Workman (Mozilla) | * Steve Workman (Mozilla) | ||
* Josh Aas (Mozilla) | * Josh Aas (Mozilla) | ||
* Wouter Wijngaards (NLNet) | * Wouter Wijngaards (NLNet Labs) | ||
The current plan is to use NLNet's libunbound along with Chromium's OS configuration detection code. We estimate (very roughly) that this will total 100-150k lines of code. | The current plan is to use NLNet's libunbound along with Chromium's OS configuration detection code. We estimate (very roughly) that this will total 100-150k lines of code. | ||
| Line 14: | Line 14: | ||
Chromium's code for reading OS configurations lives in their "src/net/dns" directory. We're primarily interested in the list of DNS servers we should be using. | Chromium's code for reading OS configurations lives in their "src/net/dns" directory. We're primarily interested in the list of DNS servers we should be using. | ||
The libunbound code is developed by [http://nlnetlabs.nl/ NLNet Labs]. The libunbound site is [http://unbound. | The libunbound code is developed by [http://nlnetlabs.nl/ NLNet Labs]. The libunbound site is [http://unbound.net unbound.net]. | ||
= Code Structure = | = Code Structure = | ||