Skip to content
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

Uses lock was taken logic in channel #306

Merged
merged 1 commit into from
Oct 18, 2019
Merged

Uses lock was taken logic in channel #306

merged 1 commit into from
Oct 18, 2019

Conversation

danielwertheim
Copy link
Collaborator

The construct as lock would use (https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/lock-statement)

Could potentially look at replacing the code with a BlockingCollection wrapping a ConcurrentQueue but that would be another PR.

@ColinSullivan1
Copy link
Member

In the past attempting to use the concurrent structures really affected performance likely due to internal additional locking we didn't need. But things could have changed....

Copy link
Member

@ColinSullivan1 ColinSullivan1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@danielwertheim danielwertheim merged commit 21f1854 into nats-io:master Oct 18, 2019
@danielwertheim danielwertheim deleted the channel_locking branch October 18, 2019 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants