3 ms·
Actually it does - the casting isn't triggered locally directly, but the castee sends a chromecast ID + app ID to Google servers which then sends appropriate pa
by izacus 11y ago
Actually it does - the casting isn't triggered locally directly, but the castee sends a chromecast ID + app ID to Google servers which then sends appropriate payload to the CC.
- rev_bird 11y agoInteresting -- that seems like it'd be introducing a lot of points to grow latency if you're casting a Chrome tab. Do you happen to know if that works differently?
- jmgrosen 11y agoChrome tabs use the same process for initiation, but then use WebRTC to actually stream the tab over the local network.
- izacus 11y agoThe actual media data / streams can of course cast directly by sending a local network URL to HTML5 part of your app, but the load of that HTML5 part is triggered via Google servers - essentially the Google server tells CC which URL to load for a certain app.