I know for sure the forward proxy crowd is using those hooks as well :)
Tracking on a TCP level is better done with connection level hooks BTW.
On Fri, 12 Jul 2019, 06:51 Sudheer Vinukonda,
wrote:
> SSN_START and SSN_CLOSE hooks can be useful for tracking/managing session
> level attributes suc
I agree with Sudheer. Plus not all plugins are in the traffic server repo.
On Thu, Jul 11, 2019, 5:51 PM Sudheer Vinukonda
wrote:
> SSN_START and SSN_CLOSE hooks can be useful for tracking/managing session
> level attributes such as context on TCP connection, rate/number of
> transactions withi
SSN_START and SSN_CLOSE hooks can be useful for tracking/managing session
level attributes such as context on TCP connection, rate/number of transactions
within the session etc. I'd vote to keep the hooks as it feels very useful even
though there isn't a plugin currently using them.
On Th
But isn't an example using kruft also kruft?
I think the only scenario for this is you hook a continuation globally on
SSN_START. You poke and prod the particular session and decide there is a
reason to sett hooks for each transaction in the session. The alternative
is the have a global hook for
> On Jul 11, 2019, at 3:58 PM, Walt Karas
> wrote:
>
> Should we deprecate this API function?
>
> The only core plugin that uses it is traffic_dump (experimental). I don't
> see it used anywhere in VzM internal plugins. Anyone using it in their
> internal plugins? (Zwoop of course can't s
Should we deprecate this API function?
The only core plugin that uses it is traffic_dump (experimental). I don't
see it used anywhere in VzM internal plugins. Anyone using it in their
internal plugins? (Zwoop of course can't say without being disappeared to
a blacksite, which actually would pro
