[getdns-api] timeouts specified as milliseconds rather than seconds

[Goyal, Neel]

Oh my - I apologize here.  I didn¹t catch that the spec was updated to
take in uint64_t already.  I think it is fine to leave as is at a uint64_t
then.

Thanks,

Neel

On 2/21/14, 6:27 AM, "Willem Toorop" <willem at nlnetlabs.nl> wrote:

>Well... not exactly a timeout, but timers in this order of magnitude are
>used in libunbound to track the root trust anchor (RFC5011).
>
>Anyway, we have been using uint64_t since I changed it (first to
>unsigned int) but later to uint64_t in the spec (on February the 8th).
>
>Do you want me to change it to uint32_t?
>
>op 20-02-14 22:17, Melinda Shore schreef:
>> On 2/20/14 11:47 AM, Wiley, Glen wrote:
>>> Since we are making this milliseconds does anyone object to making the
>>> type a uint64_t ?
>> 
>> 
>> Well, double-checking my arithmetic my previous response was overly
>> dramatic:
>> 2^33 milliseconds = 8589934592 milliseconds or about 99 days.  But I
>> still question whether or not that kind of timeout is really necessary.
>> 
>> Melinda
>> 
>
>_______________________________________________
>getdns-api mailing list
>getdns-api at vpnc.org


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