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.
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
Include and use threadpool for signaling channel messages #1761
Include and use threadpool for signaling channel messages #1761
Changes from all commits
45bc404
60471bf
189abbc
45af0e4
711b2a2
620e802
2908ba2
9224a2c
68e1c02
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we want to make this configurable instead? Is it expected customers would not require more than 5?
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.
That's why I've pointed out the location of the defines for customers to change in this README. I would have preferred to have placed them in a more common library but that would require a different constructor for slgnaling client that allows you to pass in a given threadpool. Possibly an alternative to explore later.
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.
Hmm, we can add the 2 parameters as part of SignalingClientInfo though. Having customers change the
#defs
and rebuild the SDK to be used as a dependency in another project gets messy. If we are allowing customers to configure this, having it as part of clientInfo is cleanerThere 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.
Since, we are updating the struct (and we need to) we would need to update the version table here: https://github.com/awslabs/amazon-kinesis-video-streams-webrtc-sdk-c/blob/develop/src/source/Signaling/Signaling.c#L586
Basically need to set the defaults for versions less than 2 and need internal copy. Signaling client info maintain an internal copy of all the variables, so need to do the same for this and so that the updated pSignalingClient version is passed around.