LindaTalk
Stephen Pair
spair at advantive.com
Wed Aug 22 17:37:20 UTC 2001
Rob Withers wrote:
> It should also be asynchronous, to support concurrency.
You could implement futures for async messaging to remote objects. For
example,
aRemoteStub doSomething
Would return a "future" object. Any subsequent messages sent to the
"future" object would wait for the result from "aRemoteStub doSomething"
and then delegate the message to that result (after the remote operation
completes, the future object would turn itself into a basic forwarder).
- Stephen
More information about the Squeak-dev
mailing list
|