Any way to read current tcp idle measurement?

See, "after" would allow me to set a parallel clock on the session, but doesn't give me any idea where in the idle count I am at the connection table counter. I don't want to fire anything until I get into some sort of configurable danger-zone, and keeping a timer loop in addition to an execution loop is bound to be cpu-expensive.

 

 

Not even sure if this is possible yet; whatever I do, I need to track serverside response on an HTTP transaction and drive the clientside response independently until I get serverside data back. This may not even work with the way the events tend to fire.

 

 

I'll keep working on it and see what I can do. Any other ideas out there would be helpful.