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.
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.