On May 27, 2014, at 6:08 AM, Alan M. Carroll <a...@network-geographics.com> wrote:
> James, > > Monday, May 26, 2014, 9:19:27 PM, you wrote: > >> Hi Alan, > >> So AFAICT this is not a true superset of the TSClientProtoStack API. FWIW, I >> also think that removing that API should have been reviewed. > > This proposal is not intended as a replacement for TSClientProtoStack, but to > solve a different problem (essentially logging for SPDY, although done in a > way that provides utility for other plugins) that wasn't solved by > TSClientProtoStack. > > For TSClientProtoStack, the problem was that given other structural changes > to the SPDY implementation, the API was broken and couldn't be fixed. In > particular, changing the way it was handled by the NetVCs removed the data > chain needed to provide the information. So how do you log TCP+SPDY vs. TCP+TLS+SPDY? J
