Simplify the management of the "waiting for response" state in ExchangeContext

[yufengwangca]

Problem

    CancelResponseTimer();

    // If the context was expecting a response to a previously sent message, this message
    // is implicitly that response.
    SetResponseExpected(false);

Check if we can simplify the management of the "waiting for response" state in ExchangeContext

Proposed Solution

Simplify the management of the "waiting for response" state in ExchangeContext

[issue-label-bot]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.93. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[bzbarsky-apple]

In particular, can we avoid needing two function calls that have to come together to manage the state properly?

[yufengwangca]

We are cleaning up the pending issue now, I think setting the response expected to false separately after receiving the response make the code easier to understand.

    // Since we got the response, cancel the response timer.
    CancelResponseTimer();

    // If the context was expecting a response to a previously sent message, this message
    // is implicitly that response.
    SetResponseExpected(false);

Close for now and will reopen later if needed.