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:28] – * tvcutsem | at:urbiflock [2008/08/26 19:34] – tvcutsem | ||
---|---|---|---|
Line 26: | Line 26: | ||
A flock is defined as a list of references to ' | A flock is defined as a list of references to ' | ||
- | === Predefined Flocks: | + | Predefined Flocks: |
* friend flockrs: isFriend | * friend flockrs: isFriend | ||
* nearby flockrs: isNearby | * nearby flockrs: isNearby | ||
Line 32: | Line 32: | ||
==== Architecture: | ==== Architecture: | ||
- | An ad hoc RETE-network: | + | An ad hoc RETE-network. Events are triggered by: |
- | + | * discovery: | |
- | Events are triggered by: | + | * profile changes: |
- | * discovery: joined(uid, | + | * friend changes: |
- | * profile changes: changed(uid, | + | |
- | * friend changes: friendAdded(uid, | + | |
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. | ||
+ | |||
+ | ==== Applications ==== | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
==== TODO ==== | ==== TODO ==== | ||
* [[uf: | * [[uf: | ||
* [[uf: | * [[uf: | ||
- | |||
- | ==== Applications ==== | ||
- | * [[uf: | ||
- | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag