"...Google never tested SPDY against HTTP pipelining." I use pipelining on a daily basis. And, vis-a-vis using HTTP/0.9 or 1.0, I have never been dissatisfied

"...Google never tested SPDY against HTTP pipelining." I use pipelining on a daily basis. And, vis-a-vis using HTTP/0.9 or 1.0, I have never been dissatisfied. It just works. (Before you comment, please note I never said I make my HTTP requests using a particular browser.) This is why I can never take SPDY for what they say it is (or what the silly acronym suggests). And if in fact the goal was faster speeds and in fact this alternative was faster, why should I accept the opacity it introduces? Does this protocol make it easier or more difficult to view one's own traffic? Once more, with HTTP pipelining I only request the resources I want. In my case, this does not include advertisements. Is that possible with SPDY? I do not know, but I doubt they would promote such fine grained selection as a feature. If HTTP pipelining does not work satisfactorily in [ad-supported browser], does that necessarily mean it does not work, full stop? I have tested it thoroughly and my answer is no; but I could be biased. Because HTTP pipelining has worked beautifully for me over the years, I would be quite disappointed if it were supplanted by some protocol introduced a company that relies on ad sales to stay in business. End rant. Sorry, but I am not a fan of SPDY.