Has anyone done an experiment to see what simply duplicating every TCP packet sent over wireless does? If you're in a situation where you're limited by random packet loss and not by raw bandwidth, I imagine it could help...
Obviously this is a much weaker and less efficient solution that what is proposed in the paper, but this would be trivial to implement. I believe netem allows you to simulate this.
There was an RTS game in the late 90's that did something like this. It was peer to peer, with peers broadcasting their input events to each other and running mirrored simulations in lockstep. So the bandwidth used was trivial since you can code a keypress or mouse click in just a couple bytes, but any packet loss would degrade the game for all peers. So they just duplicated the last packets input data in successive packets. No algebraic coding or any other attempt to save bandwidth, since the data was already trivial.
Comments
Has anyone done an experiment to see what simply duplicating every TCP packet sent over wireless does? If you're in a situation where you're limited by random packet loss and not by raw bandwidth, I imagine it could help...
Obviously this is a much weaker and less efficient solution that what is proposed in the paper, but this would be trivial to implement. I believe netem allows you to simulate this.
There was an RTS game in the late 90's that did something like this. It was peer to peer, with peers broadcasting their input events to each other and running mirrored simulations in lockstep. So the bandwidth used was trivial since you can code a keypress or mouse click in just a couple bytes, but any packet loss would degrade the game for all peers. So they just duplicated the last packets input data in successive packets. No algebraic coding or any other attempt to save bandwidth, since the data was already trivial.