Re:A solution for enabling UDP in the web
by scribu on Monday February 27, 2017 @09:09AM
(#13744254)
I don't think you got it straight.
> Yet another attempt to emulate a full OS-level network stack on top of HTTP
The proposed protocol does not work "on top of" HTTP. From the article:
> The basic idea is that the web backend performs authentication and when a client wants to play, it makes a REST call to obtain a connect token which is passed to the dedicated server as part of the connection handshake over UDP.
So both the handshake and the actual data transfer happen directly over UDP.
Next:
> Giving random web-pages access to RAW OS-level networking, and not just sockets, from untrusted internet JS.
The "Why not just let people send UDP?" section in the article actually explains why that would not be a good idea.
- Yet another attempt to emulate a full OS-level network stack on top of HTTP (which already runs on top of TCP/IP).
- Giving random web-pages access to RAW OS-level networking, and not just sockets, from untrusted internet JS.
How incredibly ass backwards am I if I find both proposals preposterous and dangerous?
> One solution would be for Google to make it significantly easier for game developers to integrate WebRTC data channel support in their dedicated servers.
I'm confused. Since when did Google decide what was web-standards? Is he deliberately mistaking Google for being W3C?