Open chrisjpowers opened 10 years ago
@chrisjpowers You can register the IP address of your laptop as the URL for your receiver app when setting up/registering your Chromecast. I had it set up to pull from a hosted static HTML page that was running on the python SimpleHTTP server. I used the IP address of my device (laptop) plus the port and it worked fine...
I don't believe the ChromeCast should cache it if the headers don't "promote" it to be...b/c I would think it'd be just like Chrome in that regard (ie: it should respect applicable headers)...I think.
That being said, I have done nothing with the receiver-app side of things. When I was thinking about this a while back, I was always planning on using either SSE's or Websockets for communication (likely SSE's, b/c it's simpler and not 2-way communication).
So far developing a receiver app has been a pain -- you have to constantly deploy the new receiver code to a server, and then Chromecast seems to aggressively cache, so I had to regularly reboot the Chromecast to get the newest content.
Two possible solutions:
.local
hostname, but it didn't pick it up. Maybe change DNS on the router?Thoughts?