User Tools
research:rp
Differences
This shows you the differences between two versions of the page.
|
research:rp [2010/07/31 14:32] stijnm created |
research:rp [2010/07/31 14:59] stijnm added |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | ===== Reactive Programming ===== | ||
| - | [[http:// | ||
| - | |||
| - | < | ||
| - | This page is under construction, | ||
| - | </ | ||
| - | |||
| - | ==== AmbientTalk/ | ||
| - | |||
| - | ==== Distributed Semantics ==== | ||
| - | |||
| - | Up to this point, reactive values -- and the dataflow networks constructed using them -- have been confined to the scope of a single actor. | ||
| - | |||
| - | == Contagion of Asynchronous Messages == | ||
| - | |||
| - | One mechanism to allow dataflow graphs to span multiple actors is to require that the contagion semantics apply to asynchronous messages as well as synchronous method invocations. Hence, when reactive values are passed as arguments to an asynchronous message send, that operation is lifted by the interpreter. | ||
| - | |||
| - | Instead of sending the message //as is//, a snapshot message is sent in which all reactive values are replaced with their current snapshot value. | ||
| - | |||
| - | == Ambient Behaviors == | ||
| - | |||
| - | Ambient behaviors allow reactive values to be published using a dedicated '' | ||
| - | |||
| - | The goal of these abstractions is to allow programmers to explicitly construct a distributed dependency graph, without having to encode that graph in patterns of message sending. | ||
| - | |||
| - | ==== Further Reading ==== | ||
| - | |||
research/rp.txt ยท Last modified: 2010/07/31 14:59 by stijnm
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
