This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
uf:guanotes [2009/11/18 15:07] elisag adding |
uf:guanotes [2009/11/18 15:12] elisag |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Guanotes ====== | ||
- | |||
- | ==== The concept==== | ||
- | |||
- | Guanotes application allows flockrs to post notes, called guanotes, to the ambient ( i.e any device available in the surroundings ranging from other flockr device to devices installed on public places such as KK). This is a concept similar to Stickies application in Mac but guanotes can hop from one device to another. | ||
- | |||
- | Flockrs can thus discover other flockrs guanotes, store them and exchange them later with other flockrs such that guanotes can be ' | ||
- | |||
- | Flockrs can also subscribe to a particular type of guanotes such that they are automatically notified whenever they meet a flockr carrying guanotes of that particular type. Currently, flockrs can subscribe to receive guanotes sent to a particular flock. This functionality is reminiscent to the subscription to a mailing list. | ||
- | |||
- | Another idea is that flockrs can stop the percolation of guanotes. For example, if a flockr detects that a spam guanote or a guanote with unapropiate content, it could stop its propagation. | ||
- | |||
- | ==== What is a guanote? | ||
- | |||
- | A guanote consists of a message and a receiver list (a flock or individual flockrs). Guanotes keeps track of the connected flockrs which are running the application. Guanotes applications communicate with each other (by means of the TOTAM middleware) to interchange the guanotes they carry. A guanote is propagated to another device only if a flockr belongs to the receiver list. A guanote is thus propagated through the network hopping from device to device in order to ensure that it gets received by all the targeted flockrs. | ||
- | In order to avoid flooding the network, TOTAM ensures that only flockrs belonging to the receiver list are used as //routers// (so that only potential targeted flockrs carry guanotes). | ||
- | |||
- | A guanote can be sent to a flock or an explicit collection of flockrs. In the later case end users can enumerate the targeted flockrs in the receiver list or take a snapshot of a flock. It is important to note that if the receiver is a flock, the guanote dynamically recomputes the flock definition at every device to which it gets propagated to determine the targeted flockrs. If the receiver is the snapshot of a flock, the guanote directly contains the list of targeted flockrs. | ||
- | |||
- | ==== Guanotes scenario ==== | ||
- | |||
- | {{: | ||
- | |||
- | The above figure illustrates the propagation of a guanote in a campus-based scenario. It shows six flockrs connected in Urbiflock and running the Guanotes application. The communication range of their devices is depicted with a dotted line while the colored dot on their devices denotes the gender of the flockr (pink for girls, blue for males, and grey if the gender is not set in the flockr' | ||
- | |||