Ambient-Oriented Programming

User Tools

Site Tools

Trace:
uf:proximities

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
uf:proximities [2009/11/18 13:56] – updating elisaguf:proximities [2009/11/30 16:42] (current) – proper dharnie
Line 29: Line 29:
  
 These events are received by the local flockr user object and propagated to all local proximities. Characteristic functions translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent function. These events are received by the local flockr user object and propagated to all local proximities. Characteristic functions translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent function.
- +{{:uf:proximity.jpg?507x374|:RETE-network design diagram}}
-[[:uf:proximity.jpg?507x374|RETE-network diagram]] +
  
 Alternative implementation of the RETE-network, maybe we can start from the oo matching that Tom implemented, so that Proximity functions are templates. For example:  Alternative implementation of the RETE-network, maybe we can start from the oo matching that Tom implemented, so that Proximity functions are templates. For example: 
Line 58: Line 56:
   * there must be at least one of isFriend / isNearby / wasNearby   * there must be at least one of isFriend / isNearby / wasNearby
   * there can be 0 or more doesProfileMatch functions   * there can be 0 or more doesProfileMatch functions
- 
uf/proximities.1258549007.txt.gz · Last modified: 2009/11/18 15:07 (external edit)