Open matbee-eth opened 10 years ago
@acidhax Got link to a docs for the new SDK? I haven't heard about it
https://developers.google.com/cast/docs/chrome_sender var sessionRequest = new chrome.cast.SessionRequest(chrome.cast.media.DEFAULT_MEDIA_RECEIVER_APP_ID); // Here I would put my App ID
Looking at the Tic Tac Toe example, I see that the application is able to launch on the ChromeCast without using port 8008. Everything seems to happen on port 8009. Using the ID (BFEBD3F1) instead of the name leads to 404.
Moreover, when the application is running, querying /apps/
gives a 204 instead of a 200 (and hence no content).
It seems that Google changed the protocol with its 2.0 SDK: https://plus.google.com/+SebastianMauer/posts/83hTniKEDwN
After digging a bit around, I didn't find any documentation about this new protocol. Here is what I discovered so far:
browser/extensions/api/cast_channel/cast_channel.proto
I have made some progress and put an experimental implementation in https://github.com/vincentbernat/nodecastor. This code only handles mDNS and the protobuf protocol. I don't intend to implement SSDP/DIAL. I would welcome an integration in nodecast.
Good to hear! I'll check it out :)
@vincentbernat Does your library still work with the latest chromecasts? I'll replace our chromecast handling with your stuff if so.
I can't say, I don't have any chromecast anymore. Nobody told me otherwise.
@vincentbernat Cool, will give it a shot then - thx
I can't see this documented, how would we launch an app on the Chromecast w/ the new SDK?