User Tools

Site Tools


at:urbiflock

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
Next revisionBoth sides next revision
at:urbiflock [2008/08/26 19:36] tvcutsemat:urbiflock [2008/09/04 16:32] elisag
Line 38: Line 38:
  
 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, maybe we can start from the oo matching that Tom implemented, so that proximity functions are templates. For example: 
 +
 +<code>
 +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 := "Brussel"; // city must equal this string
 +  };
 +  def greet(); // person must have a greet method
 +} taggedAs: [ Flockr ]; // object must be tagged as a Flockr
 +</code>
  
 ==== Applications ==== ==== Applications ====
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag