at:tutorial:actors
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:tutorial:actors [2007/07/18 10:43] – elisag | at:tutorial:actors [2007/07/18 11:01] – elisag | ||
---|---|---|---|
Line 203: | Line 203: | ||
Blocking a thread on a future can be a major source of deadlocks, like any form of blocking, of course. In the actor paradigm where communication between actors should remain strictly asynchronous, | Blocking a thread on a future can be a major source of deadlocks, like any form of blocking, of course. In the actor paradigm where communication between actors should remain strictly asynchronous, | ||
- | The solution proposed in the [[http:// | + | The solution proposed in the [[http:// |
- | + | ||
- | < | + | |
When a future eventually becomes resolved with a value, any messages that were accumulated by the future are forwarded asynchronously to the actual return value, such that it appears as if the original object had sent the messages to the actual return value in the first place. | When a future eventually becomes resolved with a value, any messages that were accumulated by the future are forwarded asynchronously to the actual return value, such that it appears as if the original object had sent the messages to the actual return value in the first place. | ||
+ | <note important> | ||
AmbientTalk only allows one method to be synchronously invoked on a future, the '' | AmbientTalk only allows one method to be synchronously invoked on a future, the '' | ||
+ | </ | ||
==== Working with Resolved Futures ==== | ==== Working with Resolved Futures ==== |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag