This is an old revision of the document!


  • Profiles: each flocker has a profile. There is a minimal set of properties that are present in each profile (such that proximities (e.g. a “doesProfileMatch” proximity) can be defined based on these properties).
  • Profile Dude: manages the profiles. Is responsible of propagating “changed events” to the other “reachable” flockers.
  • Changed events: when a flocker modifies his profile, the Profile Dude broadcasts a change event to all other flockers. In reaction to these events, all connected flockers should re-evaluate their proximities such that the flocks can reflect the change in the profile.
  • Caching: Each flocker keeps a cached profile of the other flockers such that the profile can be consulted offline. When a flocker is connected for which there is a cached profile, he should propagate the necessary changed events to make sure that both the cached profile and the flocks of the other flockers are updated.
uf/profiles.1219841627.txt.gz · Last modified: 2008/08/27 15:02 by alombide
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki