This is an old revision of the document!


  • Profiles: each flockr 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” flockrs.
  • Changed events: when a flockr modifies his profile, the Profile Dude broadcasts a change event to all other flockrs. In reaction to these events, all connected flockrs should re-evaluate their proximities such that the flocks can reflect the change in the profile.
  • Caching: Each flockr keeps a cached profile of the other flockrs such that the profile can be consulted offline. When a flockr 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 flockrs are updated.
uf/profiles.1219842166.txt.gz · Last modified: 2008/08/27 15:05 by alombide
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki