4 ms·
> We ended up using the WebRTC data channel ... That is an interesting approach. Unfortunately we also have to support browsers so it doesn't look like we cou
by rogerbinns 8y ago
> We ended up using the WebRTC data channel ...
That is an interesting approach. Unfortunately we also have to support browsers so it doesn't look like we could use it. (You have to type in http://something http://something to get the page that does the webrtc as far as I can tell.)
- andrewmd5 8y agoWebRTC can be used a server fashion. We opened a library that does just that: https://blog.rainway.io/real-time-communication-for-everyone-6f27e02c2f14 https://blog.rainway.io/real-time-communication-for-everyone...
- rogerbinns 8y agoUnfortunately not applicable. The problem is a user with a regular desktop browser open and has the ip address of the device (on the same subnet). They have to type something into the browser address bar. As far as I can tell, there is no way they could type something like webrtc://1.2.3.4 and would have to type something beginning with http or https. It can't be the latter because of signing issues, so we are still stuck with http.
- andrewmd5 8y agoMore than happy to offer my thoughts if you want to reach out: andrew@rainway.io