uf:totam
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
uf:totam [2014/03/19 12:28] – cfscholl | uf:totam [2020/04/28 19:41] – adding elisag | ||
---|---|---|---|
Line 20: | Line 20: | ||
Figure above illustrates how a scoped tuple is propagated through the TOTAM network. It depicts two types of locations, the blue and red locations corresponding to two teams of a multi-player game scenario where users (blue team) can use their PDA’s to chase dangerous (virtual) gangsters (red team) in the outdoors. The scope of the propagated tuple has been limited to blue locations. Figure (a) illustrates that a tuple is injected from the location with a star. This location is connected to four blue locations and one red location. As the scope of the tuple is limited to blue locations the tuple is only sent to the four blue locations. From those four locations the tuple is transitively propagated obeying the scope of the tuple until all connected blue locations are reached without being transmitted to a red location. Note that one blue location is not transitively connected to the sending device and thus does not receive the tuple. Figure (b) illustrates that a blue location moved into the range of the isolated blue location and thus, transmits the tuple to it. Again the tuple is not transmitted to nearby red locations. It is important to note from this operational sketch that the first isolated location receives a tuple without being connected at any time with the start location in which the tuple was originally inserted. | Figure above illustrates how a scoped tuple is propagated through the TOTAM network. It depicts two types of locations, the blue and red locations corresponding to two teams of a multi-player game scenario where users (blue team) can use their PDA’s to chase dangerous (virtual) gangsters (red team) in the outdoors. The scope of the propagated tuple has been limited to blue locations. Figure (a) illustrates that a tuple is injected from the location with a star. This location is connected to four blue locations and one red location. As the scope of the tuple is limited to blue locations the tuple is only sent to the four blue locations. From those four locations the tuple is transitively propagated obeying the scope of the tuple until all connected blue locations are reached without being transmitted to a red location. Note that one blue location is not transitively connected to the sending device and thus does not receive the tuple. Figure (b) illustrates that a blue location moved into the range of the isolated blue location and thus, transmits the tuple to it. Again the tuple is not transmitted to nearby red locations. It is important to note from this operational sketch that the first isolated location receives a tuple without being connected at any time with the start location in which the tuple was originally inserted. | ||
+ | |||
+ | |||
+ | |||
Line 55: | Line 58: | ||
</ | </ | ||
- | The '' | + | The '' |
- | Note that these operations | + | |
+ | In the original Linda model, read and in operations | ||
+ | |||
+ | < | ||
+ | def msgTuples := tuple: [Message, var: `from, var: `content]; | ||
+ | myTupleSpace.whenever: msgTuples read:{ | ||
+ | system.println(“Got message: “ + content + “ from: ” + from); | ||
+ | }; | ||
+ | |||
+ | myTupleSpace.whenever: | ||
+ | system.println(“ “ + from + “ says: “ + content); | ||
+ | }; | ||
+ | </ | ||
+ | |||
+ | The '' | ||
+ | |||
+ | The '' | ||
< | < | ||
Line 104: | Line 123: | ||
</ | </ | ||
- | In order to notify the removal of a tuple, TOTAM sends an antituple for the removed tuple. For every tuple there is (conceptually) a unique antituple with the same format and content, but with a different sign. All tuples injected by an application have positive sign while their antituples have a negative sign. Whenever a tuple and its antituple are stored in the same tuple space, they immediately annihilate one another, i.e. they both get removed from the tuple space. By means of antituples, TOTAM can “unsend” tuples injected to the network. | + | Upon a '' |
+ | < | ||
+ | Note that '' | ||
+ | </ | ||
Line 118: | Line 140: | ||
([[ http:// | ([[ http:// | ||
- | Note: The paper above and this webpage may have differ in the syntax for TOTAM. This webpage has been updated to fit the current implementation of TOTAM. | + | < |
+ | </ |
uf/totam.txt · Last modified: 2021/09/24 10:49 by elisag