Skip to content

Conversation

@Didjeeh
Copy link

@Didjeeh Didjeeh commented May 2, 2018

In doing so we avoid needless waiting on a semaphore to signal if you
have more than 3 simultaneous SSH clients in your application.

In doing so we avoid needless waiting on a semaphore to signal if you
have more than 3 simultaneous SSH clients in your application.
@keithallenjackson
Copy link

Wow, this might explain my low CPU usage and longer than expected wait times when connecting to 20+ devices at a time. Is the semaphore still needed at all?

@Didjeeh
Copy link
Author

Didjeeh commented Aug 19, 2018

It is a security measurement. Personally, I would leave it there as a non-static field.

@WojciechNagorski
Copy link
Collaborator

It's done on master

@WojciechNagorski WojciechNagorski added this to the 2023.0.1 milestone Dec 21, 2023
@Didjeeh
Copy link
Author

Didjeeh commented Dec 22, 2023

Nice. Thanks. Best wishes.

@WojciechNagorski
Copy link
Collaborator

The 2023.0.1 version has been released to Nuget: https://www.nuget.org/packages/SSH.NET/2023.0.1

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