It's not really associated with the Transaction, it's a session property. It would be somewhat ugly to implement that way, as you would then need to do special checks on the milestone enum to handle the session start time differently, since it's in a completely different place. The code for this function is effectively "return reinterpret_cast<ProxySession*>(ssnp)->ssn_start_time;".
It would also seem a bit odd to have things like the session VConn or ID available via the milestone interface. On Thu, Sep 19, 2019 at 1:46 PM Sudheer Vinukonda <sudheervinuko...@yahoo.com.invalid> wrote: > Hmm...Would it make sense to add this as a milestone and extend the > existing API `TSHttpTxnMileStoneGet` (and `TSMilestonesType`) to support > session start time and possibly other session level context associated to > that Txn? > Thoughts? > > > On Thursday, September 19, 2019, 11:38:47 AM PDT, Alan Carroll > <solidwallofc...@verizonmedia.com.INVALID> wrote: > > I'm playing with some session stuff and I'd like to add this, since the > data is already stored in the session, it's trivial to access. >
