yes, that is it. so when the exit node buffer, namely the stream packaging
window, is full
the receive window of the exit node will decrease
On Tue, Oct 30, 2012 at 5:48 AM, Andreas Krey wrote:
> On Mon, 29 Oct 2012 17:10:00 +, jiang song wrote:
> ...
> > There is no server-side rate control
On Mon, 29 Oct 2012 17:10:00 +, jiang song wrote:
...
> There is no server-side rate control, unless there is congestion inbetween,
> in this case the firefox browser client will
> delay or not send ack to the web server and so the web server will decrease
> its congestion window size due to ac
>
> The second one is much closer to reality. :-) The exit nodes stops
> reading from the connection to the web server when it can't forward
> the data to the client fast enough.
>
> But the web server isn't slowed down/stopped by not sending ACKs but
> rather by reducing the window size to zero. A
On Thu, 18 Oct 2012 23:42:41 +, jiang song wrote:
...
> 1) if the Tor exit node is continueing acknowledging the webserver on
> receipt of tcp segments,
> then the Tor exit node will have to cache a lot data, is it right?
> or
> 2) actually the TCP ack is from the Tor client? if the Tor exit no
