Actually, PPP over Websockets has some really interesting implications. Raw TCP/UDP in your browser is a potentially powerful thing. It's like a VPN client in your browser - once you're connected, you can bridge private networks, or establish pure TCP connections to any server on the internet, without special-case wrappers or browser-imposed WebSocket restrictions.
Comments
Actually, PPP over Websockets has some really interesting implications. Raw TCP/UDP in your browser is a potentially powerful thing. It's like a VPN client in your browser - once you're connected, you can bridge private networks, or establish pure TCP connections to any server on the internet, without special-case wrappers or browser-imposed WebSocket restrictions.
Hopefully it won't ever be used for a serious VPN; tunnelling TCP inside of TCP (or UDP inside of TCP) leads to well-known stability problems.
There's always the possibility of using WebRTC data as a transport instead of WebSockets.
It's like a 7-layer burrito with extra helpings of sour cream and guac - a bit mushy, but still a burrito.
Yes, I'd forgotten about that! Use a data channel with no retransmissions and it should work perfectly.