[reSIProcate] do DnsResult::Lookup() for every TransactionState , Is it necessary ?

[Jason Fischl]

On 12/2/05, 贾军营 <jiajunying at sict.ac.cn> wrote:
> Hi,
>     I find that Resiprocate creates new DnsResult object for every TransactionState ,so the new DnsResult object will do lookupSRV() for it's TransactionState, I don't think it's necessary. I think that it's very low effecitve and the DnsResult object can be reused . Am I right?
> Please advise.
>

DnsResult contains dns results that are specific to the transaction.
Since there may be multiple concurrent transactions, how can we reuse
the same DnsResult object between different transactions?

It might be worthwhile using a pool of DnsResult objects but I've not
noticed any indications from  profiling the stack that would indicate
that this is the best place to optimize.