On Wed, Aug 23, 2000 at 08:16:56PM -0700, Jeffrey B. Siegal wrote: > Oskar Sandberg wrote: > > It's not my area of experties (like if anything is) and I never got a > > straight answer out of anybody about choking the incoming connection. Is > > it a healthy thing to do? Will it overflow your OS buffers and screw with > > the machine in general or will TCP handle it graciously? > > I have limited access to the messages on the list at them moment, so I'm > not sure if I am answering the right question. Does this have to do > with a node accepting data from a faster connection and streaming it out > a slower one?
More generally it deals with a node trying to limit how much bandwidth it eats by choking the incoming connection. There is the question of not fucking things up on the network - but also of how well it achieves what it wants to do. > If so, there is no problem. This happens all the time. For example, > consider an old/slow system on a fast network downloading a file from a > fast server using ftp. The old system will receive packets faster > than it can process them and store the data. The TCP receive window for > that connection will fill up and the sender will stop sending data until > the window opens. > > Any system that can't handle this is seriously broken. Again, we can't ignore Windows :-). > > > _______________________________________________ > Freenet-dev mailing list > Freenet-dev at lists.sourceforge.net > http://lists.sourceforge.net/mailman/listinfo/freenet-dev > -- \oskar _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
