Ambient-Oriented Programming

User Tools

Site Tools

Trace:
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/09/04 16:23] – elisagat:urbiflock [2008/09/05 11:20] – alombide
Line 12: Line 12:
  
 ==== Modules ==== ==== Modules ====
-  * [[uf:discovery|Discovery]]: manage discovery of nearby urbiflock users 
   * [[uf:profiles|Profiles]]: manage user's profile and cache profiles of other flockrs   * [[uf:profiles|Profiles]]: manage user's profile and cache profiles of other flockrs
   * [[uf:flockr|Flockr]]: a representation of the user   * [[uf:flockr|Flockr]]: a representation of the user
Line 39: 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 functions are templates. For example: +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> <code>
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag