You’re right: HTTP adds an extra RTT and headers we don’t strictly need.
My current roadmap is:
1. Keep WebSocket as the “zero-config / browser-friendly” default.
2. Add a raw-TCP transport with a single-frame handshake:
[auth-token | caps] → ACK → binary stream starts.
3. Later, test a QUIC version for mobile / lossy networks.
So users can choose:
* plug-and-play (WebSocket)
* ultra-low-latency (raw TCP)
Thanks for the nudge this will go on the transport roadmap.
My current roadmap is:
1. Keep WebSocket as the “zero-config / browser-friendly” default. 2. Add a raw-TCP transport with a single-frame handshake: [auth-token | caps] → ACK → binary stream starts. 3. Later, test a QUIC version for mobile / lossy networks.
So users can choose: * plug-and-play (WebSocket) * ultra-low-latency (raw TCP)
Thanks for the nudge this will go on the transport roadmap.