> On May 12, 2015, at 12:48 PM, Alan M. Carroll <a...@apache.org> wrote:
> 
> My view is the SSN hooks should be called on the user agent connect / 
> disconnect, the base client session object. That would mean that for an 
> Http/2 session, the SSN hook is called only when the user agent initially 
> connects for HTTP/2 and once when the HTTP/2 connect is terminated, and *not* 
> for each transaction. Since SPDY and HTTP/2 only do one transaction per 
> stream/channel the SSN hooks aren't very useful.

Yep, “session” refers to the transport layer. The fact that H2 and SPDY 
implicitly create per-txn internal sessions is really a weakness of the 
implementation. I think it would be great if you can figure out a way to not 
invoke ssn hooks on H2 transactions (maybe just toggle 
ProxyClientSession::hooks_on?). It would also be great if getting the session 
on H2 and SPDY transactions gave the real session (not the internal one).

J

Reply via email to