Protected methods to customize client thread names. #1422
+15
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
New protected methods allow the default thread names to be customized.
Related Issue
#1421
Motivation and Context
This is useful in projects that have many threads and like to stay organized.
It is also useful when using multiple clients. Each client can name its threads differently. Without this, the threads can't be differentiated by name.
An alternative solution could be a prefix that is used for thread names, with suffixes like:
LMK if you would prefer that and I'll update the PR.
Server thread names are not considered in this PR.
How Has This Been Tested?
It's very simple, running the client tests all changes.
Types of changes
Checklist: