Simulating Latency and Bandwidth Restrictions in WCF

If you're developing WCF applications that will run over a WAN, VPN, or the public internet, then network bandwidth and latency is a concern. Messages take longer to transmit over these networks than over your local area network (LAN). As such, part of your development and testing needs to include testing the application over these typed of "slower" connection. To perform this testing there are two main options: have a connection at your disposal, or simulate one. Most of us will probably have to simulate one. There are a few projects out there that are basically bridges, typically linux based, that you put between your client and server that allow you to simulate these slower connections. If you are a Java developer, you're probably familiar with JMeter. JMeter's approach doesn't involve a bridge, but rather simulates the latency at the client. I was chatting with Peter Lin, a friend, colleague, and JMeter committer, about it one night. After he mentio...