This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
uf:flockr [2009/02/27 14:48] tvcutsem |
uf:flockr [2009/11/18 14:34] elisag |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Flockr ==== | ==== Flockr ==== | ||
+ | |||
+ | A flockr represents a user in the framework. A flockr has exactly one profile and can create and be registered to multiple flocks. In addition, a flockr can have multiple installed applications. A flockr is also the gateway that remote parties can use to get information about the user. | ||
Each Flockr contains following info : | Each Flockr contains following info : | ||
Line 12: | Line 14: | ||
* a map of usernames to far refs to connected flockrs. | * a map of usernames to far refs to connected flockrs. | ||
- | A Flockr | + | A Flockr |
- | The remote interface is the entity that gets exported to the ambient. | + | |
Profile won't get exported to the ambient but it has to proactively asked to the Flockr. This allows: 1) Remote Flockr does not need to ask the [[Profile]] again (if you rediscover the Flockr) if it didn't change and 2) allow the Flockr to decide who can actually see its [[Profile]]. | Profile won't get exported to the ambient but it has to proactively asked to the Flockr. This allows: 1) Remote Flockr does not need to ask the [[Profile]] again (if you rediscover the Flockr) if it didn't change and 2) allow the Flockr to decide who can actually see its [[Profile]]. |