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
With current implementation wrapping this method with per request or per action behaviors is imposible. Consumer does use context.
The text was updated successfully, but these errors were encountered:
Gobonoid
changed the title
Message sink PutMessage should take context as a parameter
Message sink PutMessage could take context as a parameter
Jul 26, 2018
I see the need for this in the consumer case, where the message handling itself may block or take a long time. I'm wondering about the producer case though. Why would you expect this to block? Is it as simple as the broken being slow for some reason, or have I missed something bigger?
For easier extendability I think Put message should have signature like:
With current implementation wrapping this method with per request or per action behaviors is imposible. Consumer does use context.
The text was updated successfully, but these errors were encountered: