Skip to content
This repository was archived by the owner on Jul 9, 2023. It is now read-only.

Conversation

@honfika
Copy link
Collaborator

@honfika honfika commented May 16, 2017

Doneness:

  • Build is okay - I made sure that this change is building successfully.
  • No Bugs - I made sure that this change is working properly as expected. It doesn't have any bugs that you are aware of.
  • Branching - If this is not a hotfix, I am making this request against develop branch

Task.WhenAll(handlerTasks).Wait();

//why is the sender null?
ClientCertificateSelectionCallback.InvokeParallel(null, args);
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Why is the sender null here? It can be the sender parameter of the calling method (which is an SslStream) or the ProxyServer object. (+Same question in ServerCertificateSelectionCallback)

Copy link
Owner

Choose a reason for hiding this comment

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

Probably I didn't care about it before. We can pass ProxyServer, since SslStream is less useful for doing anything with it.

@justcoding121 justcoding121 merged commit 585ec8e into justcoding121:develop May 16, 2017
justcoding121 added a commit that referenced this pull request Oct 18, 2017
connection count locking + usings sorted
justcoding121 added a commit that referenced this pull request Oct 18, 2017
connection count locking + usings sorted
justcoding121 added a commit that referenced this pull request Oct 19, 2017
connection count locking + usings sorted
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants