On May 19, 2014, at 10:46 AM, Alan M. Carroll <a...@network-geographics.com> wrote:
> James, > >> I still don't understand this focus on client session chaining. AFAICT there >> is no client session chaining other than an implementation detail in the >> current SPDY implementation. I don't see how client session is a general >> concept at all. > > In order to do other things (such as logging) successfully, there must be > some chain from an HttpSM instance to the SpdyClientSession. Where should > this link be? It seems simplest and most comprehensible to me to chain it via > the client session. It also makes it nicely hierarchial, that is a protocol > stack. OK, so we are not talking about a chain of client sessions, we are talking about a chain (graph?) of transaction states rooted from a client session? That makes a lot more sense to me and sounds very promising. > Here is a picture of what I think is a reasonable data structure. Note the > only change between what is there now and this diagram is the addition of > parent links from the HttpClientSession. >
