You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the HTTP application it's possible to inject an original request reference into request-scoped providers. However, there's no such functionality for microservices.
Expected behavior
It would be great to have something similar to Request provider but in Microservices. For example, Context provider.
In case of Microservices, context might be an object that contains pattern and transmitted data, at least for TCP Microservice.
CONTEXT {
pattern,
data
}
What is the motivation / use case for changing the behavior?
Having access to Request (context) provider permit to instantiate services per request based on the context.
For example:
Can you please provide a simple example of how to print out the request context? I am trying to print the subject of the received message in my MessagePattern controller.
For example if I subscribe to @MessagePattern("user.id.>") I want to be able to get the subject of the request so I can split the string get get the send ID, for example if subject is user.id.abcdef I need the abcdef part.
I'm submitting a...
Current behavior
In the HTTP application it's possible to inject an original request reference into request-scoped providers. However, there's no such functionality for microservices.
Expected behavior
It would be great to have something similar to Request provider but in Microservices. For example, Context provider.
In case of Microservices, context might be an object that contains pattern and transmitted data, at least for TCP Microservice.
What is the motivation / use case for changing the behavior?
Having access to Request (context) provider permit to instantiate services per request based on the context.
For example:
Environment
What do you think?
The text was updated successfully, but these errors were encountered: