uf:flockr
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| uf:flockr [2009/02/27 14:48] – tvcutsem | uf:flockr [2009/11/30 16:49] (current) – *correct dharnie | ||
|---|---|---|---|
| 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 : | ||
| - | * [[Profile]] | + | * [[profiles|Profile]] |
| * list of its [[Flock|flock]]s where it is registered. | * list of its [[Flock|flock]]s where it is registered. | ||
| * Note: maybe it should be stored in the profile. | * Note: maybe it should be stored in the profile. | ||
| 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 [[profiles|Profile]] again (if you rediscover the Flockr) if it didn't change and 2) allow the Flockr to decide who can actually see its [[profiles|Profile]]. |
| The remote interface receives 3 types events from the network (join, left and changeProfile) and notifies the local interface of the Flockr which notifies the necessary [[Proximities]] objects. | The remote interface receives 3 types events from the network (join, left and changeProfile) and notifies the local interface of the Flockr which notifies the necessary [[Proximities]] objects. | ||
| Line 21: | Line 22: | ||
| The local interface contains also receives the events on changes on the buddyList. | The local interface contains also receives the events on changes on the buddyList. | ||
| - | The buddyList is a list of its friends Flockrs. The editor for [[Flock|flock]]s will allow that the [[Profile]] can be consulted offline. When a Flockr is connected for which there is a cached [[Profile]], | + | The buddyList is a list of its friends Flockrs. The editor for [[Flock|flock]]s will allow that the [[profiles|Profile]] can be consulted offline. When a Flockr is connected for which there is a cached [[profiles|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. |
| * xtof suggestion to implement this: | * xtof suggestion to implement this: | ||
uf/flockr.1235742503.txt.gz · Last modified: 2009/11/18 14:34 (external edit)