[API 0.505] "resolver_type" now "resolution_type"

Renamed in the response from getdns_context_get_api_information()
This commit is contained in:
Willem Toorop 2014-09-03 15:42:11 +02:00
parent c27034ff9d
commit 3b9c1270c2
6 changed files with 5 additions and 5 deletions

View File

@ -201,7 +201,7 @@ a bindata containing a printable string of the version of the DNS API implemente
.IP implementation_string .IP implementation_string
a bindata containing a printable string set by the implementation a bindata containing a printable string set by the implementation
.IP resolver_type .IP resolution_type
an int equal to GETDNS_RESOLUTION_RECURSING or GETDNS_RESOLUTION_STUB an int equal to GETDNS_RESOLUTION_RECURSING or GETDNS_RESOLUTION_STUB
.IP all_context .IP all_context

View File

@ -375,7 +375,7 @@ Set to GETDNS_EXTENSION_TRUE to add the following to the top level of the respon
.I implementation_string .I implementation_string
(bindata) : string set by this library's implementer as a build or version indicator (bindata) : string set by this library's implementer as a build or version indicator
.br .br
.I resolver_type .I resolution_type
(int) : GETDNS_CONTEXT_RECURSING or GETDNS_CONTEXT_STUB depending on how the context is configured (int) : GETDNS_CONTEXT_RECURSING or GETDNS_CONTEXT_STUB depending on how the context is configured
.br .br
.I all_context .I all_context

Binary file not shown.

BIN
spec/getdns-0.505.tgz Normal file

Binary file not shown.

View File

@ -2435,7 +2435,7 @@ API.</li>
be human-readable, and it might have information in it useful to an application developer (but it doesn't be human-readable, and it might have information in it useful to an application developer (but it doesn't
have to).</li> have to).</li>
<li><code>resolver_type</code> (an int) is the type of resolver that the API is acting as in this context: <li><code>resolution_type</code> (an int) is the type of resolver that the API is acting as in this context:
<code>GETDNS_RESOLUTION_RECURSING</code> or <code>GETDNS_RESOLUTION_STUB</code> (it will be <code>GETDNS_RESOLUTION_RECURSING</code> or <code>GETDNS_RESOLUTION_STUB</code> (it will be
a recursing resolver unless the application changed this in a context.</li> a recursing resolver unless the application changed this in a context.</li>
@ -2446,7 +2446,7 @@ getdns_pretty_print_dict() for debugging.</li>
<h1>9. The Generated Files</h1> <h1>9. The Generated Files</h1>
<p>There is <a href="getdns-0.504.tgz">a tarball</a> that includes the .h files, <p>There is <a href="getdns-0.505.tgz">a tarball</a> that includes the .h files,
the examples, and so on. The examples all make, even though there is no API implementation, based the examples, and so on. The examples all make, even though there is no API implementation, based
on a pseudo-implementation in the tarball; see make-examples-PLATFORM.sh. Note that this currently builds fine on a pseudo-implementation in the tarball; see make-examples-PLATFORM.sh. Note that this currently builds fine
on the Macintosh and Ubuntu; help is definitely appreciated on making the build process on the Macintosh and Ubuntu; help is definitely appreciated on making the build process

View File

@ -1814,7 +1814,7 @@ getdns_context_get_api_information(getdns_context* context) {
} }
r = getdns_dict_util_set_string(result, "version_string", PACKAGE_VERSION); r = getdns_dict_util_set_string(result, "version_string", PACKAGE_VERSION);
r |= getdns_dict_util_set_string(result, "implementation_string", PACKAGE_URL); r |= getdns_dict_util_set_string(result, "implementation_string", PACKAGE_URL);
r |= getdns_dict_set_int(result, "resolver_type", context->resolution_type); r |= getdns_dict_set_int(result, "resolution_type", context->resolution_type);
settings = priv_get_context_settings(context); settings = priv_get_context_settings(context);
r |= getdns_dict_set_dict(result, "all_context", settings); r |= getdns_dict_set_dict(result, "all_context", settings);
getdns_dict_destroy(settings); getdns_dict_destroy(settings);