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/09/05 11:45] – cfscholl | at:urbiflock [2008/09/05 11:52] – elisag | ||
---|---|---|---|
Line 30: | Line 30: | ||
* nearby friend flockrs: isFriend & isNearby | * nearby friend flockrs: isFriend & isNearby | ||
- | [[uf: | + | WhiteBoard Drawings: |
+ | * [[uf: | ||
==== Architecture ==== | ==== Architecture ==== | ||
Line 39: | Line 40: | ||
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. | ||
- | |||
- | As a first implementation of the RETE-network, | ||
- | |||
- | < | ||
- | def flockrTemplate := template: { | ||
- | def name := *; // wildcard, can be anything | ||
- | def age := constraint: { _ < 25 }; // must be younger than 25 | ||
- | def address := template: { | ||
- | def street := *; //any street,but street name must be filled | ||
- | def city := " | ||
- | }; | ||
- | def greet(); // person must have a greet method | ||
- | } taggedAs: [ Flockr ]; // object must be tagged as a Flockr | ||
- | </ | ||
==== Applications ==== | ==== Applications ==== |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag