anism) to do the cleanup on TXN_CLOSE.\
>
I don't see how your answers are related to my questions so I'll let others
consider this.
> -Original Message-----
> From: Walt Karas
> Sent: Thursday, December 7, 2023 9:27 AM
> To: dev@trafficserver.apache.org
> Subject: Re: [E] [TSAPI] TSTxnAlloc
>
>
>
nism) to do the cleanup on TXN_CLOSE.
-Original Message-
From: Walt Karas
Sent: Thursday, December 7, 2023 9:27 AM
To: dev@trafficserver.apache.org
Subject: Re: [E] [TSAPI] TSTxnAlloc
ot ATS resources.
>
> -Original Message-
> From: Walt Karas
> Sent: Wednesday, December 6, 2023 9:25 PM
> To: dev@trafficserver.apache.org
> Subject: Re: [E] [TSAPI] TSTxnAlloc
>
> Could we move Arena.h to tscpp/util, and just add:
>
> Arena & tsapi::txnArena(T
able state. And the finalizers are about cleaning up UDTs,
not ATS resources.
-Original Message-
From: Walt Karas
Sent: Wednesday, December 6, 2023 9:25 PM
To: dev@trafficserver.apache.org
Subject: Re: [E] [TSAPI] TSTxnAlloc
Could we move Arena.h to tscpp/util, and just add:
Are
Could we move Arena.h to tscpp/util, and just add:
Arena & tsapi::txnArena(TSHttpTxn txn);
For your finalizer example, when would that be better than using
Cleanup.h? That is, when would it be better than having the vector be a
data member of the TxnAuxData class you provide as a parameter to th
