uf:totam
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
uf:totam [2010/01/21 17:35] – elisag | uf:totam [2010/01/21 17:36] – elisag | ||
---|---|---|---|
Line 8: | Line 8: | ||
==== Design ==== | ==== Design ==== | ||
- | 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. |
uf/totam.txt · Last modified: 2021/09/24 10:49 by elisag