Mojo C++ bindings: MultiplexRouter more aggressively dispatch queued messages.

Mojo C++ bindings: MultiplexRouter more aggressively dispatch queued messages.

This CL allows MultiplexRouter to dispatch multiple queued messages to clients
without returning to the message loop.

This way we may starve other tasks on the same thread, but we have been doing
the same thing in the non-associated-interface case (see
Connector::ReadAllAvailableMessages). So it is probably okay.

BUG=590495
Committed: https://crrev.com/51fec73df69c66596985a9037bc0665529327507
Cr-Commit-Position: refs/heads/master@{#381514}

[yzshen1, 2016-03-16 17:43:58]

yzshen@chromium.org changed reviewers:
+ rockot@chromium.org

[yzshen1, 2016-03-16 17:44:00]

Hi, Ken.

Please take a look. Thanks!

This CL probably doesn't improve the numbers of the ipc_mojo_perftests, because
that is a pingpong test that sends a single message back-and-forth, so there
aren't multiple queued messages.

[Ken Rockot(use gerrit already), 2016-03-16 18:05:57]

Cool, LGTM!

[yzshen1, 2016-03-16 18:08:11]

The CQ bit was checked by yzshen@chromium.org

[commit-bot: I haz the power, 2016-03-16 18:08:45]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1808583003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1808583003/1

[commit-bot: I haz the power, 2016-03-16 19:46:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-16 19:48:21]

Description was changed from

==========
Mojo C++ bindings: MultiplexRouter more aggressively dispatch queued messages.

This CL allows MultiplexRouter to dispatch multiple queued messages to clients
without returning to the message loop.

This way we may starve other tasks on the same thread, but we have been doing
the same thing in the non-associated-interface case (see
Connector::ReadAllAvailableMessages). So it is probably okay.

BUG=590495
==========

to

==========
Mojo C++ bindings: MultiplexRouter more aggressively dispatch queued messages.

This CL allows MultiplexRouter to dispatch multiple queued messages to clients
without returning to the message loop.

This way we may starve other tasks on the same thread, but we have been doing
the same thing in the non-associated-interface case (see
Connector::ReadAllAvailableMessages). So it is probably okay.

BUG=590495

Committed: https://crrev.com/51fec73df69c66596985a9037bc0665529327507
Cr-Commit-Position: refs/heads/master@{#381514}
==========

[commit-bot: I haz the power, 2016-03-16 19:48:22]

Patchset 1 (id:??) landed as
https://crrev.com/51fec73df69c66596985a9037bc0665529327507
Cr-Commit-Position: refs/heads/master@{#381514}