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
A lot of simulation processing power is spent on PROCESSes which are busy-waiting for the receipt for some message. This could be alleviated by providing a callback to the COURIER which is triggered when an appropriate message arrives.
This comes with several difficulties: a PROCESS has both passive listeners (as installed in its message dispatch table) which are selectively triggered (via their guards) as well as active listeners installed via commands. The longevity of either of these classes is questionable. Additionally, callbacks will have strange timing properties: what hardware-realistic value would time have when a callback is triggered? (Recently, there's also the added complication of peruse-inbox?.)
The text was updated successfully, but these errors were encountered:
A lot of simulation processing power is spent on
PROCESS
es which are busy-waiting for the receipt for some message. This could be alleviated by providing a callback to theCOURIER
which is triggered when an appropriate message arrives.This comes with several difficulties: a
PROCESS
has both passive listeners (as installed in its message dispatch table) which are selectively triggered (via their guards) as well as active listeners installed via commands. The longevity of either of these classes is questionable. Additionally, callbacks will have strange timing properties: what hardware-realistic value wouldtime
have when a callback is triggered? (Recently, there's also the added complication ofperuse-inbox?
.)The text was updated successfully, but these errors were encountered: