* Robert Collins <robe...@robertcollins.net> [100517 22:03]: > Given that pipelining is broken by design, that the HTTP WG has > increased the number of concurrent connections that are recommended, > and removed the upper limit - no. I don't think that disabling > pipelining hurts anyone - just use a couple more concurrent > connections. > > -Rob
I was unaware that pipelining was considered "broken by design", so I was trying to say that if there was an easy way for apt to choose between pipelining and no pipelining (if it wasn't specifically set by the admin) that would handle most of the cases, that was better than disabling by default a feature that was beneficial to many. If pipelining is considered broken, and concurrency is preferred, I'm perfectly happy with that. ...Marvin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100518120244.gl1...@cleo.wdw
