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 [2010/01/21 17:35] – updating elisag | uf:totam [2010/10/20 16:28] – elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== Tuples on the Ambient (TOTAM) ===== | ===== Tuples on the Ambient (TOTAM) ===== | ||
- | TOTAM is a communication abstraction | + | TOTAM is an extension |
- | The basic communications API of the framework provides means to address and communicate with individual flockrs by means of remote objects references. | + | |
- | However, communicating with a large amount of flockrs in this fashion does not scale (as it would require | + | |
- | Instead, we have designed a dedicated communication abstraction for flock communication called //TOTAM//. | + | |
- | ==== Design | + | ==== Motivation |
- | The original idea was to build a framework similar to TOTA [[http:// | + | The original idea was to build a framework similar to [[http:// |
However, in TOTA tuples are sent to all communication partners in range. Upon arrival at the receiver side, the tuple itself decides whether it has to be stored in that tuple space. By transmitting tuples potential malicious or non-intended users are provided with sensitive information. Not only does sending all tuples blindly to all communication partners in range raise privacy issues, it also creates a network traffic overhead. | However, in TOTA tuples are sent to all communication partners in range. Upon arrival at the receiver side, the tuple itself decides whether it has to be stored in that tuple space. By transmitting tuples potential malicious or non-intended users are provided with sensitive information. Not only does sending all tuples blindly to all communication partners in range raise privacy issues, it also creates a network traffic overhead. | ||
- | To solve this issues, we extended TOTA with dynamically scoped tuples | + | To solve this issues, we extended TOTA with dynamically scoped tuples |
Another goal was to implement TOTAM as a general framework so that we can then instantiate our TOTAM with guanote objects for the [[: | Another goal was to implement TOTAM as a general framework so that we can then instantiate our TOTAM with guanote objects for the [[: | ||
Line 72: | Line 69: | ||
def decideSleep() -> boolean | def decideSleep() -> boolean | ||
</ | </ | ||
+ | |||
+ | Ideas: | ||
+ | |||
+ | TOTA could be combined with the RETE engine we built for the characteristic functions, in the future to reason about multiple tuples. | ||
decideSleep() is there for discontinuous decidePropagation functions. for example, tuples that should be only propagated every Tuesday could not implemented with TOTA because the propagation protocol only gets called once. We change this by providing decideSleep() that gets called when you decide not to propagate. Like this a tuple can still be propagate at a later point in time, despite the fact that the decidePropagation function has evaluated to false at a certain moment. | decideSleep() is there for discontinuous decidePropagation functions. for example, tuples that should be only propagated every Tuesday could not implemented with TOTA because the propagation protocol only gets called once. We change this by providing decideSleep() that gets called when you decide not to propagate. Like this a tuple can still be propagate at a later point in time, despite the fact that the decidePropagation function has evaluated to false at a certain moment. |
uf/totam.txt · Last modified: 2021/09/24 10:49 by elisag