What is unique about NetEqualizer ‘s throttling mechanism?
Almost all Internet communications have a client/server model where the client is sending requests and the server is sending data. This is true for ftp transfers, streaming video and streaming audio. Even if the client and server are sending UDP packets there is always a client/server relationship. The slowing or delaying of client requests is a much better way to throttle the data back than slowing or queuing the data coming from the server. The NetEqualizer limits bandwidth by looking at the large user(s) of bandwidth and slowing requests from the client. This is radically different from the methods employed by WFQ, TOS and other packet shaping tools. It is the only method that allows you some actual control over Internet traffic coming into your network. The biggest advantage to slowing down client requests is that you get at the source of traffic problems without employing expensive and complex queuing algorithms.
