Originally Posted by meburdick
This is not how casting works.
What you are describing is sort of like a "remote control" for a specific app within the TV. Casting has nothing to do with controlling anything actively running on the TV - it's merely a different way to bring content to the panel to display. Instead of using an HDMI cable to bring the content to the panel, you are sending content over a WiFi network to the "receiver" on the TV. You don't even need to have a specific app installed on the TV in order to cast content from that app from a different device.
Actually what I said is how it works. So I reached out to the chromecast team, (I reached out because I started a video then turned off my phone, which indicates the TV is shouldering all the load. As it turns out the TV has a chromecast app built in which has all the chromecast supported apps available), anyway and this is how it works:
John C9:22 AM
OK let me verify this with you. A person opens a Youtube video on their phone. They click the cast icon and sent it to their TV. What really happens from there is...
John C9:23 AM
The phone reaches out to the TV on some port no doubt, then says "this is a YT video, this is the address of the file, start playing at this timestamp...
John C9:24 AM
The TV gets that info, then using its own internet connection (obviously) reaches out for the address the phone told it to play, and opens the chromecast YT app, and starts playing the video.
John C9:24 AM
Is this correct?
You just elaborated what I have said earlier in your own words. ☺️
So basically my suspicion was correct that casting is just a hand off of a link to the TV to play. It appears that the chromecast app will hand off the work to a few built in apps (like netflix), but generally it uses the watered down chromecast player for most everything on the TV. But the TV is doing all the work.