Skip to content
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.

Sign up for GitHub

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

Jump to bottom

mDNS discovery should run continuously #16

Open
jtara opened this issue Apr 5, 2017 · 1 comment
Open

mDNS discovery should run continuously #16

jtara opened this issue Apr 5, 2017 · 1 comment
Assignees
@jtara

Comments

@jtara
Copy link
Member

jtara commented Apr 5, 2017 •
edited
Loading

Currently, mDNS discovery is done only on the first cast. After casting to any discovered devices, mDNS discovery is terminated.

If any Chromecast devices are added/removed to the network (which might match requested device(s)) after application start, the web service would have to be restarted.

The current code conflates mDNS discovery with casting. (first cast).

mDNS discovery should run constantly, keeping track of available Chromecast devices. Casting should be entirely separate, and rely on list/object of available devices.

See also #15.
@jtara jtara self-assigned this Apr 5, 2017
@jtara jtara mentioned this issue Apr 5, 2017
Open
@jtara jtara changed the title DDNS discovery should run continuously mDNS discovery should run continuously Apr 5, 2017
@jtara jtara closed this as completed May 10, 2017
@jtara
Copy link
Member Author

jtara commented Sep 3, 2017 •
edited
Loading

Issue was erroneously closed. This was not implemented.

@jtara jtara reopened this Sep 3, 2017
@jtara jtara mentioned this issue Sep 3, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jtara jtara

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jtara