New candidate JEP: 506: Scoped Values
Josiah Noel
josiahnoel at gmail.com
Tue Apr 15 14:51:21 UTC 2025
I suppose I'm just not sure what feedback to give beyond it works like I
thought it would. I've been using it in one of our high traffic APIs since
java 21. Currently the service is on JDK 24 and I haven't noticed any
problems with the preceding java versions either.
I use it to store request data that would otherwise be put in an MDC
context. I then have a custom logback encoder which extracts the values and
put them into the json log statement.
On Tue, Apr 15, 2025, 10:16 AM David Alayachew <davidalayachew at gmail.com>
wrote:
> Correct
>
> On Tue, Apr 15, 2025, 8:59 AM Davor Hrg <hrgdavor at gmail.com> wrote:
>
>> Am I reading this correctly?
>>
>> Does this mean Scoped Values will be fully available (not hidden behind
>> the preview flag) in Java 25 ?
>>
>>
>>
>> On Mon, Apr 14, 2025 at 9:43 PM Mark Reinhold <mark.reinhold at oracle.com>
>> wrote:
>>
>>> https://openjdk.org/jeps/506
>>>
>>> Summary: Introduce scoped values, which enable a method to share
>>> immutable data both with its callees within a thread, and with child
>>> threads. Scoped values are easier to reason about than thread-local
>>> variables. They also have lower space and time costs, especially when
>>> used together with virtual threads (JEP 444) and structured concurrency
>>> (JEP 505).
>>>
>>> - Mark
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20250415/cf0c7e1b/attachment.htm>
More information about the loom-dev
mailing list