[getdns-api] return_api_information and return_call_debugging extensions

[Goyal, Neel]

One other question / clarification needed.  return_api_information talks
about the following field:

all_context (a dict) with names for all the types of context. This can be
used with getdns_pretty_print_dict() for debugging.

I am not sure what this means - any information would be much appreciated.



On 2/18/14, 4:59 PM, "Paul Hoffman" <paul.hoffman at vpnc.org> wrote:

>On Feb 18, 2014, at 1:09 PM, Goyal, Neel <ngoyal at verisign.com> wrote:
>
>> In looking at the api and debugging extensions (Section 3.6), I wanted
>>to
>> get the group opinion on a couple of items.
>> 
>> - What do you think about removing the return_api_information extension
>> altogether and making this a synchronous call on the context itself?
>> Something like struct getdns_dict*
>> getdns_context_get_api_information(context);  This information feels
>>like
>> it belongs in its own call rather than within a query (which seems even
>> stranger if it was asynchronous).
>
>Calling it a "helper function" would make it more palatable to the
>strongly async folks.
>
>There was some reason that we made this an extension, but I'm forgetting
>it now. Making it a helper function seems fine.
>
>> - The return_call_debugging extension has a "query_to" field which is
>>the
>> address to which the query was sent.  In the case of recursive mode,
>>would
>> this just be the root server contacted, or would it make more sense to
>>be
>> a list of servers hit (or none if it was fetched from cache)?
>
>That's a good question, and I don't think we thought of it. I would
>support the latter.
>
>--Paul Hoffman


_______________________________________________
getdns-api mailing list
getdns-api at vpnc.org