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 11:30] – elisag | at:tutorial:actors [2008/03/13 16:49] – added tvcutsem | ||
---|---|---|---|
Line 201: | Line 201: | ||
We have described a future as a placeholder for the return value of an asynchronous message send which is eventually // | We have described a future as a placeholder for the return value of an asynchronous message send which is eventually // | ||
- | 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. In the actor paradigm where communication between actors should remain strictly asynchronous, |
The solution proposed in the [[http:// | The solution proposed in the [[http:// | ||
+ | |||
+ | As an example of a pipeline of message sends, consider the following code: | ||
+ | |||
+ | < | ||
+ | def booleanFuture := remoteObject< | ||
+ | booleanFuture< | ||
+ | ... | ||
+ | } ifFalse: { | ||
+ | ... | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | In this example, the message '' | ||
==== Working with Resolved Futures ==== | ==== Working with Resolved Futures ==== | ||
Line 271: | Line 284: | ||
</ | </ | ||
- | Finally, it is useful to know that '' | + | Finally, it is useful to know that '' |
< | < |
at/tutorial/actors.txt · Last modified: 2020/02/05 21:26 by elisag