Efficient usage of a fat but high latency link with the implementation of TCP to increase performance is achievable.
If you're dealing with a high-latency connection that has a large bandwidth, and you want to run a TCP-based application over it, you might end up with problems due to limited TCP windows. That's where Showerhead comes in. Showerhead sets up a proxy between two machines running Showerhead; one end connects to your client, and the other connects to your server. Your data is then sent over multiple TCP streams and reassembled on the other end.
With Showerhead, you can run as many connections as you need, up to at least 20 (tested by netcatting large files). The number of streams used is configurable, allowing you to optimize the proxy for your particular connection.
While I haven't personally tested Showerhead on a high-latency connection with a large bandwidth, the tool has worked seamlessly for me in other situations. That being said, I do wish the Showerhead project was better documented and more user-friendly, as it is a useful tool for those dealing with similar networking issues.
With Showerhead, you can run as many connections as you need, up to at least 20 (tested by netcatting large files). The number of streams used is configurable, allowing you to optimize the proxy for your particular connection.
While I haven't personally tested Showerhead on a high-latency connection with a large bandwidth, the tool has worked seamlessly for me in other situations. That being said, I do wish the Showerhead project was better documented and more user-friendly, as it is a useful tool for those dealing with similar networking issues.
What's New
Version 195: N/A