Fix some MultiplexRouter behavior for sync messages
Two small fixes:
- ProcessTasks was unintentionally scoping the
interface id for a sync message task, so
an unprocessed task would then get pushed
back onto the queue for kInvalidInterfaceId
- Unprocessed task pointer was being pushed back
onto the sync message queue after moving the
task ptr back into the task queue, so the sync
message queue entry would always be null.
Also minor cleanup to ProcessFirstSyncMessageForEndpoint
to wipe out empty entries in sync_message_tasks_ when
possible.
R=yzshen@chromium.org
BUG=
Review-Url: https://codereview.chromium.org/2035893003
Cr-Commit-Position: refs/heads/master@{#397719}
CrOS-Libchrome-Original-Commit: b22a087001308e421c1c4b6fa7cf33d0b9b2d4e7
1 file changed