Add GetStatusAsync and StopAsync to ReceiverChannel #7
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.
Connecting to a session that a different sender created is now possible by calling
StopAsync()
on theReceiverChannel
which then under the covers callsGetStatusAsync()
(GET_STATUS command) on the receiver channel and then uses the session from the retrieved status to call STOP on the receiver to stop the playing media.Something like this:
Note that there now are
StopAsync()
methods on both theReceiverChannel
andMediaChannel
objects (with different uses). I did not try to implementPauseAsync()
onReceiverChannel
, although it might be possible.