It is possible for
update to be called many times in between calls to
view. That means that messages can sometimes be built against a stale version of the Model. It also means that messages can be processed asynchronously for performance; imagine if
view had to run in lock-step.
It occurs to me that I do not know how the
subscriptions function is invoked in the TEA runtime loop. Does it get called after every single
update invocation? Or is it tied to the animation frame like
view? Or something else?
I’m curious to know if
subscriptions can ever be out of sync with the
Model, and whether this can lead to spurious events? I don’t have a specific bug I am trying to fix; just wondering.