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 revisionBoth sides next revision
at:urbiflock [2008/08/26 19:31] – tvcutsemat:urbiflock [2008/08/26 19:34] – tvcutsem
Line 32: Line 32:
  
 ==== Architecture: ==== ==== Architecture: ====
-An ad hoc RETE-network: +An ad hoc RETE-network. Events are triggered by: 
- +  * discovery: ''joined(uid,flockr)'' / ''left(uid,flockr)'' 
-Events are triggered by: +  * profile changes: ''changed(uid,flockr,updatedProfile)'' 
-  * discovery: joined(uid,flockr) / left(uid,flockr) +  * friend changes: ''friendAdded(uid,flockr)'' / friendRemoved(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. 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.
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag