Unfortunately this is another message I somehow didn't get in my inbox.
Replying to it via lists.a.o is not a great experience but is the best I can do.
On 2024/03/20 13:51:56 Volkan Yazıcı wrote:
> I agree with the way Piotr dissects the problem. I think `ScopedContext`,
> even though it has its
> On Mar 18, 2024, at 2:39 AM, Piotr P. Karwasz wrote:
>
> Hi,
>
> Given the ongoing context data propagation in three Github
> issues/PRs/discussions (cf. [1], [2] and [3]). I think we should move
> the debate to the mailing list, which guarantees the maximal reachout.
>
> == Problem summar
1. I am experimenting with adding Thread support to ScopedContext as we speak.
It should be straightforward.
I am not sure we ever want to deal with ScopedValue. ScopedContext provides the
same functionality plus integration with logging.
Ralph
> On Mar 20, 2024, at 4:22 AM, Piotr P. Karwasz
I agree with the way Piotr dissects the problem. I think `ScopedContext`,
even though it has its own merits, doesn't address the problem reported by
users. They simply want a new logger associated with some additional
context data.
*[See my comments below.]*
On Mon, Mar 18, 2024 at 10:40 AM Piotr
Hi Ralph,
On Tue, 19 Mar 2024 at 07:45, Ralph Goers wrote:
> 2. The links you provide describe the problem of passing contexts to threads
> magnificently. Unfortunately, they solve it by requiring you NOT to use
> standard JDK tooling for managing threads. I am not prepared to be dependent
> o
