-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: use cache for push in AMQP plugin #612
Conversation
7c859ae
to
33fbecc
Compare
|
||
var pool = senders_.GetOrAdd(address, | ||
s => new ObjectPool<SenderLink>(parallelismLimit_, | ||
async token => new SenderLink(new Session(await ConnectionAmqp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So each Link have its own Session. Is it something we want to keep?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for now yes
_) => new ValueTask<bool>(!link.IsClosed && | ||
!link.Session.IsClosed))); | ||
|
||
await pool.WithInstanceAsync(sender => sender.SendAsync(new Message(Encoding.UTF8.GetBytes(msgData.TaskId)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You did not pass the cancellation token to SendAsync.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not take cancellation tokens
No description provided.