(NASA has their wacky ways around the issue for ISS residents, something like VNC to a ground-based browser IIRC.)
(NASA has their wacky ways around the issue for ISS residents, something like VNC to a ground-based browser IIRC.)
I wonder if there's still a more "API level" way to handle things, though, rather than making your computer into a dumb frame buffer client with extremely low responsiveness to typing/scrolling.
Maybe they could run a headless browser on Earth, and use a protocol like the Chromecast does to synchronize its DOM state to a "browser proxy" in space—like a higher-level, domain-specific version of the X11 protocol. That'd still have latency for JavaScript-based webapp UI, though... maybe the JS could be split and its state synchronized so that the "server" handles timer triggers, while the "client" handles input events.
Wait, VNC? Won't that use oodles more bandwidth than proxying HTTP?
This is one of my favorite NT4 tidbits :)
of course the same is true of ground stations... I'm not actually sure how they do it but they probably don't need as high-gain of an antenna to reach them.