Re: Bandwidth throttling
Re: Bandwidth throttling
- Subject: Re: Bandwidth throttling
- From: Peter Sichel <email@hidden>
- Date: Fri, 16 Oct 2009 14:47:05 -0400
On Oct 16, 2009, at 1:26 PM, email@hidden wrote:
Does anyone have an idea how applications (e.g. bittorrent clients,
download managers) throttle their own bandwidth?
If an application you are writing is sending, you can limit how much
you send per unit time.
For download or receive traffic, there are two basic techniques
sometimes know as "packet shaping":
(1) Queue (hold) and selectively drop. TCP is adaptive and will
throttle back when Acks are delayed or lost. This generally works for
UDP as well.
(2) TCP has its own flow control mechanism know as the "advertised
window size". The receiver tells the sender how many bytes it can
send ahead of what has already been acknowledged (the receive
window). To throttle a TCP sender, you simply dole out window
advertisements at whatever rate you wish. The TCP stack normally does
this for you, but you have some control over the window size.
My own IPNetRouterX implements a form of this and can throttle
individual TCP connections if desired.
- Peter Sichel
Sustainable Softworks
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden