On Mon, May 13, 2013 at 5:58 PM, William Chan (陈智昌) <willchan@chromium.org>wrote: > That's kinda why I don't really want to take this change as is now. I'd > rather wait for more implementation experience. AFAICT, we have at least 3 > very large scale SPDY server deployments (Google, Twitter, and Facebook), > and none of them have yet asked for this to be fixed. Maybe they're fine > with just not calling read() in these situations. I'd rather wait for > people deploying SPDY & HTTP/2.0 draft implementations to come back and say > that this is actually a problem and we need to fix it. > > +1 for running code. We're at a point where most changes should be influenced by that; imo.
Received on Monday, 13 May 2013 22:27:47 UTC