Device discovery? about rust-cast HOT 3 CLOSED

Thanks to @CyrosX, we have a support for a device discovery via mDNS in the rust_caster example! Refer to #18 for more details.

from rust-cast.

Hey @andrewshadura,

Unless I’m mistaken, there currently isn’t any code to discover new Chromecast devices, and the only way to use them is to know the IP address beforehand having discovered it by some other means.

Yeah, you're correct.

Would you consider implementing that or including some examples of performing discovery by other means (I’ve no idea at the moment how to do zeroconf discovery in Rust)?

I'd definitely accept PR if someone comes up with the solution for that (either as a part of this crate or just as an example)!

When I was toying with this crate in the past, I either used avahi-browse directly, like in rust-caster example (it can filter proper service types that Chromecast exposes) or used multicast-dns crate (basically a rough subset of Avahi bindings I wrote long time ago).

If you or anyone else have a desire to improve this crate even further, I think the proper direction would be to migrate to Open Screen Protocol and Google's openscreen library (assuming their license is permissive enough) that would give us a cross-platform access for the device discovery, support for all existing and future Chromecast-like devices (including Chromecast), and so on.

from rust-cast.

In case it's helpful to someone, the Gnomecast application pychromecast library written in Python auto detects all casting abled devices in the network. Perhaps that functionality can be translated to rust-cast.

This is the function that returns all of the connected casting devices.

from rust-cast.