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 [2009/11/18 15:10] – adding elisag | uf:totam [2010/10/20 16:26] – adding 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 ==== | ==== Design ==== | ||
- | We have reused the concepts developed by | + | The original idea was to build a framework similar to [[http:// |
- | The original idea was to build a framework similar to TOTA to be able to exchange and percolate guanotes. Tota proposes relying on distributed | + | However, in TOTA tuples |
- | TOTAM has been designed to be independent from service discovery. So, Guanotes | + | To solve this issues, we extended TOTA with dynamically scoped tuples resulting in the TOTAM (" |
+ | |||
+ | Another goal was to implement TOTAM as a general framework so that we can then instantiate our TOTAM with guanote objects for the [[: | ||
==== API ==== | ==== API ==== | ||
Line 68: | Line 67: | ||
// if true -> tuple gets unexported and deleted from local TS. | // if true -> tuple gets unexported and deleted from local TS. | ||
//new operation not in TOTA | //new operation not in TOTA | ||
- | def decideDie() -> boolean | + | def decideSleep() -> boolean |
</ | </ | ||
- | decideDie() 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 | + | 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 |
uf/totam.txt · Last modified: 2021/09/24 10:49 by elisag