On 05/19/2014 09:49 AM, Wang Weijun wrote:
After some discussion with mit and heimdal lead engineers, I don't want to
support ms at the moment. mit does not use kdc_timeout at all and heimdal's
internal presentation is of seconds.
So this is my plan: support "s" but if unspecified treat it as "ms". There will
be a release notes describing this. This won't automatically fix the case for the bug reporter but
at least give him a workaround -- use the 's' unit for interop.
Does this sound clean?
Sounds good to me. Since the reporter was already changing the default
value, it's not unreasonable to require them to add a 's'.
--Sean
Thanks
Max
On May 18, 2014, at 23:12, Xuelei Fan <xuelei....@oracle.com> wrote:
On May 18, 2014, at 9:48 PM, chris...@zoulas.com wrote:
On May 18, 10:06am, weijun.w...@oracle.com (Wang Weijun) wrote:
-- Subject: Re: RFR 8036779: sun.security.krb5.KdcComm interprets kdc_timeout
| How about this? I will support "s" and "ms" units ("ms" is not defined by o=
| ther vendors though). But will still try to be a little smart when there is=
| no unit.
Heuristics can make the situation worse; they are difficult to document
and explain to users. But if java is going to support ms, let's coordinate
with heimdal and mit to make them support it too.
+1
Xuelei
christos
