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 [2009/11/18 13:37] – updating elisagat:urbiflock [2009/11/18 13:45] – elisag
Line 13: Line 13:
 ==== Terminology ==== ==== Terminology ====
  
-  * Flock: a group of proximate users +  * Flockr: a user of the Urbiflock framework 
-  * Flockr: a user of the urbiflock framework+  * Flock: a group of users
   * To flock: to become part of a group   * To flock: to become part of a group
  
Line 38: Line 38:
 WhiteBoard Drawings:  WhiteBoard Drawings: 
   * [[uf:Design|Design]]   * [[uf:Design|Design]]
- 
-==== Architecture ==== 
-An ad hoc RETE-network. Events are triggered by: 
-  * discovery: ''joined(uid,flockr)'' / ''left(uid,flockr)'' 
-  * profile changes: ''changed(uid,flockr,updatedProfile)'' 
-  * friend changes: ''friendAdded(uid,flockr)'' / ''friendRemoved(uid,flockr)'' 
- 
-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 ==== ==== Applications ====
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag