Lines Matching full:callbacks
1461 // The AnswerAllLocalQuestionsWithLocalAuthRecord routine walks the question list invoking client callbacks, using the "m->CurrentQuestion"
1465 // More generally, if we invoke callbacks from within a client callback, then those callbacks could deregister other
1466 // records, thereby invoking yet more callbacks, without limit.
1585 // Note that with all the client callbacks going on, by the time we get here all the
3502 // If new questions are created as a result of invoking client callbacks, they will be added to
3578 // If new questions are created as a result of invoking client callbacks, they will be added to
3608 // If new questions are created as a result of invoking client callbacks, they will be added to
3710 // callbacks for old records are delivered before callbacks for newer records.
3799 // then CheckCacheExpiration may give this question add/remove callbacks, and it's not yet ready for that.
3802 // client callbacks, which may delete their own or any other question. Our mechanism for detecting
3803 // whether our current m->NewQuestions question got deleted by one of these callbacks is to store the
3811 // CacheRecordRmv() both use that themselves when walking the list of (non-new) questions generating callbacks.
5798 // can result in user callbacks which may change the record list and/or question list.
5800 // "ResponseRecords" list, because we don't want to risk user callbacks deleting records
6925 // to immediately to generate answer callbacks, or we call ScheduleNextCacheCheckTime()
8688 // Specifically, question callbacks invoked as a result of this call cannot themselves make API calls.
