ntextVsScopedContextBenchmark.java
> >
> > Ralph
> >
> >> On Aug 14, 2024, at 7:23 AM, John Engebretson
> wrote:
> >>
> >> Ralph, I get a 404 on that link to your code, could you please verify
> the
> >> link is good?
> >>
>
>> On Aug 13, 2024, at 12:43 PM, Piotr P. Karwasz
> wrote:
> >>
> >> Hi John,
> >>
> >> On Tue, 13 Aug 2024 at 21:10, John Engebretson
> wrote:
> >>> HI - just curious when the updated ThreadContextMap will be available?
> >>&g
HI - just curious when the updated ThreadContextMap will be available?
The latest release is 2.23.1, over five months ago.
Thanks! :)
John
I'm sorry for being unclear! What I mean is that the current code built
on 8 will behave and perform identically to the current code built on 17.
Is that correct?
John
On Thu, May 30, 2024 at 10:04 AM Ralph Goers
wrote:
>
>
> > On May 30, 2024, at 7:43 AM, John Eng
I agree on the complexity argument - and FWIW we still have many apps on
JDK 8 and are intimidated by the Spring upgrade, so I understand that. :)
Sounds like we agree there's no runtime impact?
John
On Thu, May 30, 2024 at 9:31 AM Ralph Goers
wrote:
>
>
> > On May 30, 2024, at 6:37 AM, En
:
>
>
> > On May 24, 2024, at 11:10 AM, Piotr P. Karwasz
> wrote:
> >
> > Hi John,
> >
> > On Fri, 24 May 2024 at 17:17, John Engebretson
> wrote:
> >> As
> > I stated several times, 'ThreadContext.get()` is a mistake, because it
>
Hi, my company is looking forward to the performance improvements
associated with 2.24.0 (specifically #2330). Most of our applications rely
on MDC or CloseableThreadContext and the performance benefits will be
widespread. The long-debated ScopedContext is not significant to us. Can
we set a ta
