Extreme tunnelling

OK, the first attempt was encouraging in that people could play, but not so good in that it was hardly playable. Back to the drawing board...

The Idea

Same as the last one, but use 20 TCP connections, and send data down a different one each time. In theory TCP connections won't use any bandwidth at all when they're idle, so they won't lag if there's no data :) So, by having that many TCP connections, when one lags, the others won't - so it should pick up after lags and frozen streams really quickly. It's a bit more complicated though because you need multiple TCP connections that all serve the same client Q3 connection.

The Result

Success! Finally a playable Quake3 connection for people behind firewalls. However, because of the way I'd written it...I had to run the tunnel server (because no one else can), and I have to manually set server ips. It was a right hassle, and far from ideal still. But heh, it worked, project complete, yeah?...