0

Clarify Mojo guarantees ordering within each pipe

The current doc stops short of explicitly stating that Mojo guarantees
ordering within each message pipe. Clarify this point.

Bug: None
Change-Id: I22d9ebe0ff74ee7e524eebebbdb1cbe9e026fb56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4443038
Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Hong Xu <xuhong@google.com>
Cr-Commit-Position: refs/heads/main@{#1132623}
This commit is contained in:
Hong Xu
2023-04-19 19:18:28 +00:00
committed by Chromium LUCI CQ
parent 861fa5670e
commit a2be4a3528

@ -85,9 +85,10 @@ configure some new behavior. The implementation may be inadvertently relying on
this message arriving *before* some other tangentially related message sent to
the same frame shortly after the same navigation event.
Mojo does not (and in fact cannot) make any strict ordering guarantees between
separate message pipes, as message pipes may be freely moved across process
boundaries and thus cannot necessarily share a common FIFO at all times.
While Mojo guarantees strict ordering within each message pipe, Mojo does not
(and in fact cannot) make any strict ordering guarantees between separate
message pipes, as message pipes may be freely moved across process boundaries
and thus cannot necessarily share a common FIFO at all times.
If the two messages described above were moved to separate Mojo interfaces on
separate message pipes, renderer behavior could break as the first message may