Are there notes somewhere that outline our plans for supporting server-side sessions in the TS API? Are we eventually going to have distinct handles for client-side and server-side sessions (maybe TSHttpCsSsn andTSHttpSsSsn, with TSHttpSsn a deprecated synonym for TSHttpCsSsn) ? Will start/stop hooks fire for server-side sessions, and will there be distinct hoods for client and server side sessions?
Currently on master it looks like TSHttpSsn instances can map to a ProxySession pointer or a Http1ServerSession pointer in core ATS. It seems like the plugin is supposed to keep track of whether the handle is for a client or server side session. In some places we check that the plugin is keeping track properly: https://github.com/apache/trafficserver/blob/master/src/traffic_server/InkAPI.cc#L7493 but generally we don't: https://github.com/apache/trafficserver/blob/master/src/traffic_server/InkAPI.cc#L4774
