If I were to design a protocol for browser UDP packets with a dedicated server, what would be a good name for it. I'm thinking "speednet"
-
-
If we just had this one thing, everything else could be built. I plan to create a reference implementation in C with libsodium.
-
To answer the original question, although multiple channels over UDP in QUIC relieves head of line blocking for unrelated data
- 3 more replies
New conversation -
-
-
Games need the ability to send and receive UDP packets to a server.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But just letting the browser send UDP packets to any IP address is a huge security hole
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
so it follows that any solution that would be acceptable in the browser would need a handshake and may only send ...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
UDP packets to that server on establishing connection
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Building on DTLS seems reasonable, but since DTLS leaves authentication to the user
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think it's flawed and exposes any system build on that to zombie clients
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
what I think is required is a minimal system that transfers auth from the web server to the UDP server(s) ...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
with a short lived connect token constructed w. AEAD. That way only authenticated clients may connect to the UDP server
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.