Add support for generic srt socket options set/get. #4325
Merged
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.
This PR adds support for generic SRT socket options:
input.srt
andoutput.srt
are now bare bonesrt.socket
with no method. This decluters the API documentation.srt.socket
is added to decorate a SRT socket with its methodson_socket
callback is introduced that is executed just after setting our default socket options to give the user flexibility to set their own and/or monitor a socket etc.Here's an example use to set latency on incoming sockets. Please note that this is more tricky than it seems: setting the latency on the incoming socket instead of the listening socket results in a timeout!
Ref: #4256