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

[Goyal, Neel]

We could then use uint32_t - I think uint16_t maxing @ 65 seconds is too
little, though if that timeout is ever hit, then there are probably other
issues at play.  Maybe uint64_t is overkill and uint32_t suffices.

On 2/20/14, 4:17 PM, "Melinda Shore" <melinda.shore at nomountain.net> wrote:

>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
>
>-- 
>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