Lines Matching refs:transactions
93 LIST_REMOVE(transactions_by_scope, t->scope->transactions, t);
100 set_remove(c->transactions, t);
144 * transactions, and it's much lower than the space of IDs. */
210 LIST_PREPEND(transactions_by_scope, s->transactions, t);
342 * transactions, as that might destroy other
343 * transactions in our list. Hence, in order to be
345 * transactions, take a GC lock on all of them
617 /* Checks whether the auxiliary DNSSEC transactions of our transaction have completed, or are still
674 /* Are there ongoing DNSSEC transactions? If so, let's wait for them. */
678 if (r == 0) /* We aren't ready yet (or one of our auxiliary transactions failed, and we shouldn't validate now */
681 /* See if we learnt things from the additional DNSSEC transactions, that we didn't know before, and better
689 /* All our auxiliary DNSSEC transactions are complete now. Try
996 /* There are DNSSEC transactions pending now. Update the state accordingly. */
1321 * For mDNS, we want to coalesce as many open queries in pending transactions into one single
1322 * query packet on the wire as possible. To achieve that, we iterate through all pending transactions
1328 LIST_FOREACH(transactions_by_scope, other, t->scope->transactions) {
1347 * One of the 'other' transactions will fire later and take care of the rest.
1773 /* Checks whether our transaction our any of the auxiliary transactions couldn't do DNSSEC. */
2071 /* Invoked whenever any of our auxiliary DNSSEC transactions completed its work. If the state is still PENDING,
2072 we are still in the loop that adds further DNSSEC transactions, hence don't check if we are ready yet. If
2153 /* We found a DS transactions for the SOA/NS
2526 /* Copy all validated RRs from the auxiliary DNSSEC transactions into our set of validated RRs */