This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
uf:flockr [2008/09/04 16:06] elisag |
uf:flockr [2009/11/30 16:49] dharnie *correct |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Flockr ==== | ||
- | Each Flockr contains following info : | ||
- | * [[Profile]] | ||
- | * list of its [[Flock]]s where it is registered. | ||
- | * Note: maybe it should be stored in the profile. | ||
- | * list of its [[Flock]]s. | ||
- | * predefined [[Flock]]s. | ||
- | * user-defined [[Flock]]s. | ||
- | |||
- | A Flockr should have a local and remote interface. | ||
- | The remote interface is the entity that gets exported to the ambient which at least contains: | ||
- | * [[Profile]] | ||
- | * predefined [[Flock]]s | ||
- | |||
- | [[Flockr]] actually should be able to decide who can see him. How? maybe Profile? | ||
- | |||
- | The local interface receives the 3 types events from the discovery. | ||
- | |||
- | There should be a list of its friends [[Flockr]]s such that the [[Profile]] can be consulted offline. When a Flockr is connected for which there is a cached [[Profile]], | ||
- | * xtof suggestion to implement this: | ||
- | * Make " | ||
- | * This abstraction could be used for any list of [[Flockr]]s that need offline Profile visualization. Maybe useful also for applications. | ||
- | |||
- | ==== API ==== |