[getdns-api] resolution_type vs. resolver_type
Goyal, Neel
ngoyal at verisign.com
Tue Aug 12 16:04:18 CEST 2014
I would vote to change the dictionary key to ³resolution_type² - less
risky to change a string in a dictionary vs. a function sig.
On 8/12/14, 10:00 AM, "Melinda Shore" <melinda.shore at nomountain.net> wrote:
>Hi:
>
>Shumon Huque was asking why the resolver_type attribute
>in the Python bindings wasn't seeming to be set correctly.
>I'd coded this up directly from the API spec without
>thinking about it very carefully, and on closer inspection
>of the specification it turns out that while the setter
>function in the spec is called context_set_resolution_type(),
>the dictionary key in the data returned from
>context_get_api_information() is "resolver_type". I think
>these should probably be brought into alignment, although
>I have no strong feelings about which is preferable.
>
>Melinda
>
>--
>Melinda Shore
>No Mountain Software
>melinda.shore at nomountain.net
>
>"Software longa, hardware brevis."
>_______________________________________________
>getdns-api mailing list
>getdns-api at vpnc.org
_______________________________________________
getdns-api mailing list
getdns-api at vpnc.org
More information about the spec
mailing list