title: Are multiple TCP connections a viable alternative to UDP? (WebSockets)
body: <p>I'm investigating WebSockets as a means of running an online game where there are multiple players on-screen and position updates for all are streamed to each client.</p>
  
  <p>Unfortunately WebSockets are TCP only, so if there is congestion in the pipes, the stream will suffer.</p>
  
  <p>My idea was to mitigate this as far as possible by making multiple WebSocket connections from the client (Same server, multiple ports?) and have the server stream updates to these connections in a round-robin manner.</p>
  
  <p>If one stream is congested then the next update might make it through on another connection allowing the client to catch-up. Out-of-order stale updates are discarded.</p>
  
  <p>Is this a viable solution? Am I talking networking nonsense? Or will it likely be a small mitigation for far too much engineering effort?</p>