You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a suggestion from Michel.
Imagine we have a sender who is sending "$.redraw" messages, each of which
gives some parameter defining the redraw.
One can conceive of a listener who wishes only to hear the most recent
redraw message - any messages they "miss" are not of interest.
Thus, if the sender sends:
* redraw 1
* redraw 2
* redraw 3
and the listener then does "get next message", it only wants to read the
"redraw 3" message, and not the preceding (presumably now irrelevant)
messages.
This can probably be emulated by just having a loop that reads until there
are no more messages (and then "using" the last message), but that's
clumsy, and probably error prone.
Considerations:
1. What happens if the sender flags the message with ALL_OR_WAIT or
ALL_OR_FAIL (presumably this listener should not be considered when
judging whether this message can be sent?)
2. What happens if one of the messages is marked URGENT?
Original issue reported on code.google.com by [email protected] on 18 Mar 2010 at 3:33
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 18 Mar 2010 at 3:33The text was updated successfully, but these errors were encountered: