> On Nov 15, 2017, at 8:33 AM, Alan Carroll <solidwallofc...@oath.com.INVALID> > wrote: > > 1) Generally the hook names aren't conjugated, more like > 'TS_VCONN_CONNECT_HOOK' and 'TS_VCONN_ACCEPT_HOOK'. > 2) 'TS_VCONN_CLOSE_HOOK' is required. That's one the the issues that > sparked all of this, the inability to have a hook where VConn related data > can be cleaned up. >
Sorry for the late reply here. I think if we’re going to add a new “registry” for the VConn slots, we probably also should break the Ssn and Txn registry as well. I’m slightly torn on it, it seems more convenient if a plugin just registers for a single slot, and use that for all 3 APIs. On the flip side, separate registries could, in theory at least, allow for better utilization of the slots. But, I think we should be consistent regardless of which route we take. Meaning, if we add this new registry, as another 8.0.0 incompatible change, we should break the registry for Txn and Ssn’s. — leif
