Ivan,
I'm a bit confused :) Unless I misread the initial suggestion, the idea is
to provide a public API to create the context. In other words, it will be
up to the end user to create this context properly, which affects the
business code - and that's exactly where I see an issue.
The examples
Hello!
OK, it sounds good. I can see that these were already merged. Can you check
if these tickets may be closed?
Also, there's a new crop of "feedbacks" on the dev list.
Thanks,
--
Ilya Kasnacheev
чт, 30 сент. 2021 г. в 01:59, Nikita Safonov :
> Hi Ilya!
>
> Currently we respond to users
+1 to have service proxy context.
> 11 окт. 2021 г., в 09:43, Ivan Daschinsky написал(а):
>
> Val, Pavel both of you are right, but on the other hand there are some
> other tasks
>
> 1. Distributed tracing.
> 2. Custom metrics/measurements
> 3. Auth and some related tasks (i.e. ingests full
Val, Pavel both of you are right, but on the other hand there are some
other tasks
1. Distributed tracing.
2. Custom metrics/measurements
3. Auth and some related tasks (i.e. ingests full User info by calling some
auth service in middleware).
Do you both think that this is a good idea in
