This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
uf:totam [2020/04/28 19:32] elisag |
uf:totam [2021/09/24 10:41] elisag update of protocols |
||
---|---|---|---|
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 59: | Line 60: | ||
The '' | The '' | ||
- | In the original Linda model, read and in operations were provided to return a copy of the tuple and remove the tuple from the tuple, respectively. Those operations where blocking. TOTAM, inspired by Lime, offers non-blocking variants of these operations | + | In the original Linda model, read and in operations were provided to return a copy of the tuple and remove the tuple from the tuple, respectively. Those operations where blocking. TOTAM, inspired by Lime, offers non-blocking variants of these operations: |
< | < | ||
Line 72: | Line 73: | ||
</ | </ | ||
- | The '' | + | The '' |
- | The '' | + | The '' |
< | < | ||
Line 83: | Line 84: | ||
Note that the network facilities are disabled by default, so before injecting something in the network, the '' | Note that the network facilities are disabled by default, so before injecting something in the network, the '' | ||
- | A tuple injected | + | ==== Tuple' |
+ | |||
+ | Similar to TOTA, when devices come into communication range, tuples are replicated and shared amongst devices part of the TOTAM system. The propagation of tuples in the ``TOTAM network'' | ||
< | < | ||
Line 100: | Line 103: | ||
</ | </ | ||
- | However, other propagation protocols can be created and attached to a tuple before being injected in the network as follows: | + | Custom |
< | < | ||
Line 115: | Line 118: | ||
</ | </ | ||
- | The '' | + | The '' |
< | < | ||
- | // sends an antituple to notify the removal of this tuple. | + | // cancels the propagation of the tuple to new devices in the TOTAM network. |
+ | publication.cancel(); | ||
+ | // sends an antituple to notify the removal of this tuple in devices which carry a copy. | ||
publication.retract(); | publication.retract(); | ||
</ | </ | ||
- | In order to notify | + | Upon a '' |
+ | Upon a '' | ||
+ | < | ||
+ | Note that '' | ||
+ | </ | ||