Configurator.shutdown() simply delegates to LoggerContext.stop().
LoggerContext.stop() does several things, and it is not quite correct to
say that zero timeout mean don't wait. It mean don't wait for background
threads, but it will still wait for appenders and filters, depending on how
they inter
Do we need a "don't wait" case?
On Mon, Oct 3, 2016 at 11:35 PM, Gary Gregory
wrote:
> Right now, in the Configurator.shutdown 0 means do not wait at all.
>
> We could have:
>
> > 0 wait
> = 0 don't wait
> -1 wait forever which could map to Long.MAX_VALUE, TimeUnit.DAYS. What
> where they thinki
On Mon, Oct 3, 2016 at 3:46 PM, Matt Sicker wrote:
> With the proposed Mars colonisation, yeah, we could use TimeLocation as
> well.
>
Locale.MARS !
Gary
>
> On 3 October 2016 at 16:35, Gary Gregory wrote:
>
>> Right now, in the Configurator.shutdown 0 means do not wait at all.
>>
>> We could
With the proposed Mars colonisation, yeah, we could use TimeLocation as
well.
On 3 October 2016 at 16:35, Gary Gregory wrote:
> Right now, in the Configurator.shutdown 0 means do not wait at all.
>
> We could have:
>
> > 0 wait
> = 0 don't wait
> -1 wait forever which could map to Long.MAX_VALUE
Right now, in the Configurator.shutdown 0 means do not wait at all.
We could have:
> 0 wait
= 0 don't wait
-1 wait forever which could map to Long.MAX_VALUE, TimeUnit.DAYS. What
where they thinking stopping at DAYS instead of YEARS? Clearly we are
missing a TimeLocation.EARTH as well ;-)
Gary
