at:urbiflock
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2008/08/26 19:30] – tvcutsem | at:urbiflock [2008/09/05 11:52] – elisag | ||
---|---|---|---|
Line 12: | Line 12: | ||
==== Modules ==== | ==== Modules ==== | ||
- | * [[uf: | ||
* [[uf: | * [[uf: | ||
* [[uf: | * [[uf: | ||
Line 31: | Line 30: | ||
* nearby friend flockrs: isFriend & isNearby | * nearby friend flockrs: isFriend & isNearby | ||
- | ==== Architecture: ==== | + | WhiteBoard Drawings: |
- | An ad hoc RETE-network: | + | * [[uf:Design|Design]] |
- | Events are triggered by: | + | ==== Architecture ==== |
- | * discovery: joined(uid, | + | An ad hoc RETE-network. |
- | * profile changes: changed(uid, | + | * discovery: |
- | * friend changes: friendAdded(uid, | + | * profile changes: |
+ | * friend changes: | ||
These events are received by the local flockr user object and propagated to all local proximities. Proximities translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent proximity. | These events are received by the local flockr user object and propagated to all local proximities. Proximities translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent proximity. | ||
Line 43: | Line 43: | ||
==== Applications ==== | ==== Applications ==== | ||
* [[uf: | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
* [[uf: | * [[uf: | ||
* [[uf: | * [[uf: | ||
- | ==== TODO ==== | + | ==== To think about ==== |
- | * [[uf: | + | * [[uf: |
* [[uf: | * [[uf: | ||
- |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag