-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support disconnecting from a chromecast #28
Comments
This is really weird. If anybody has any thoughts how to implement this I would be really interested to talking you about this. |
Maybe not the cleanest way, but what happens if you stop sending ping pong messsages on the heartbeat channel? Or if you just close the socket connection? |
I want to make it so after disconnection you can connect to a new chromecast or same one. So basically disposing the underlying socket, stopping the heartbeat and then creating them again or something like that |
Does the new connection need to be done from the same chromecastclient object? I think it is also possible just to create a new instance and optionally to implement idisposable in chromecastclient? (Just looking at the different options) |
Yep. But then the events are bit tricky. Since the event handlers are hooked into the client and if recreated you loose them. But I think that might be the best way to go |
Any more progress on this? I try to use SharpCaster, but without any way to disconnect and reconnect, it's pretty useless for my scenario. |
I got pretty far but started doing other stuff. I will take a look at this on the coming weekend, will post here the status on Sunday. |
This is now supported on dev branch. Might take a while for all of it to be pushed to master and nuget. |
No description provided.
The text was updated successfully, but these errors were encountered: