uf:flockr
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
uf:flockr [2008/09/04 15:55] – elisag | uf:flockr [2008/09/04 16:06] – elisag | ||
---|---|---|---|
Line 10: | Line 10: | ||
A Flockr should have a local and remote interface. | 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: | The remote interface is the entity that gets exported to the ambient which at least contains: | ||
- | * [[Profile]] | + | |
- | * predefined [[Flock]]s | + | * predefined [[Flock]]s |
[[Flockr]] actually should be able to decide who can see him. How? maybe Profile? | [[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. | The local interface receives the 3 types events from the discovery. | ||
- | Not sure where to place: | + | 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 ==== | ==== API ==== |
uf/flockr.txt · Last modified: 2009/11/30 16:49 by dharnie