Yes, this is primarily for logging / tracking, the purpose being to have an ID that is the same for all transactions on the same user agent session. The UUID stuff doesn't fit that criteria. Additionally, since the data is already sitting there and it's similar to TxnID, it seems a reasonable addition.
On Sat, May 12, 2018 at 4:48 AM, Leif Hedstrom <zw...@apache.org> wrote: > I think there is an API to get txn count on a session already. I believe > this API is intended for logging, but then it’s slightly lacking (see > below). It does provide symmetry with the TXN ID though. > > Also, remember there are UUID APIs that provide unique IDs as well. And > they are supported by e.g header_rewrite. > > I think it’d be useful to at lest add this new feature to header rewrite, > which can then be used with a custom log. > > — Leif > > > On May 12, 2018, at 00:13, Shu Kit Chan <chanshu...@gmail.com> wrote: > > > > How are we going to use this Id? > > I don't think any API takes the Ssn Id as argument. Right? > > > > Or are you simply just trying to figure out how many txns reuse the ssn ? > > > > Thanks. > > > > Kit > > > > On Fri, May 11, 2018 at 3:42 PM, Alan Carroll > > <solidwallofc...@oath.com.invalid> wrote: > >> +1 > >> > >>> On Fri, May 11, 2018 at 11:08 AM, Zeyuan Yu <zeyu...@gmail.com> wrote: > >>> > >>> int64_t TSHttpSsnIdGet(TSHttpSsn ssnp) > >>> It returns the unique client session identifier for ssnp. This API > would be > >>> useful for transaction monitor plugin. > >>> > >>> Docs here: > >>> https://github.com/dyrock/trafficserver/blob/api_ssn_id/ > >>> doc/developer-guide/api/functions/TSHttpSsnIdGet.en.rst > >>> > >>> > >>> -- > >>> [image: work-eat-sleep--400090.jpg] > >>> > >>> *Zeyuan Yu* > >>> Assoc Software Development Engineer, Oath > >>> > >>> m: 217.369.5086 > >>> > >
