3 ms·

You do its called the webrtc data channel.

• torginus 4y ago
  Yeah and its an absolute PITA to set up, and a nightmare from the ops perspective, I'm not even sure what even are you supposed to use on the server side.
  • beebeepka 4y ago
    The client is fairly easy, imho. Did you mean setting up the infrastructure? Because yeah, hard to do properly
    • torginus 4y ago
      Yeah the infra (NAT traversal is hell), and I'm unsure how I would hook something like that up to a web server like Flask. Either you get a proper WebRTC implementation like Google's which is huge and does a ton of other stuff, or you talk to another browser peer to peer.
      • meheleventyone 4y ago
        Or use something specific like libdatachannel https://libdatachannel.org/ https://libdatachannel.org/ If you’re using WebRTC data channels in a client server config then infra is no more complex than a regular setup because the server will almost certainly have an external facing IP address. People should really try using WebRTC as well because you can get the full pipeline setup for a toy demo in a couple of slow days. I did whilst also writing my own signalling server in Go without having used Go before! It’s certainly not any more complex than rolling all the stuff the article is talking about on top of raw UDP.
      • easrng 4y ago
        If you're doing nodejs you can just `npm i wrtc` and get the same api as in the browser.