4 ms·
I mean if it's built in the browser it's likely using WebRTC under the hood. Might not be the same techniques they described in their article but all the negoti
by shehryarrr 8y ago
I mean if it's built in the browser it's likely using WebRTC under the hood. Might not be the same techniques they described in their article but all the negotiation and transport is built on open source then. Likely also using MS Desktop Duplication API and Media Foundation.
Not sure why the time you started building it matters but hasn't moonlight-chrome been around for even longer? https://github.com/moonlight-stream/moonlight-chrome https://github.com/moonlight-stream/moonlight-chrome
- andrewmd5 8y ago> it's likely using WebRTC under the hood We use multiple connection methods actually. WebRTC data channels can fail to connect a lot and we don't want people to be left out in the rain. So we built our own PKI and global dynamic DNS on top of Let's Encrypt to ensure connectivity https://blog.rainway.io/encryption-for-all-3383217e4194 https://blog.rainway.io/encryption-for-all-3383217e4194 (we made sure to sponsor them as well) >MS Desktop Duplication API & Media Foundation Are too much of a black box and we needed to be able to fine-tune both our capturing and encoding. >moonlight-chrome Is a Chrome App (discontinued) which relies on native code whereas Rainway is HTML5 and requires no plugins and works in all spec compliant browsers. We