Ambient-Oriented Programming

User Tools

Site Tools

Trace:
uf:flockr

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
uf:flockr [2008/09/04 16:04] – elisaguf: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]]   * [[Profile]]
Line 16: Line 15:
  
 [[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.
  
Line 23: Line 22:
     * Make "cached" object abstraction. It is just a proxy object which forwards to the online version when it's online, otherwise the catched version. Every update, replaces the cached version with a clone. In other words, keeps a cached object that gets updated when you are connected.     * Make "cached" object abstraction. It is just a proxy object which forwards to the online version when it's online, otherwise the catched version. Every update, replaces the cached version with a clone. In other words, keeps a cached object that gets updated when you are connected.
     * This abstraction could be used for any list of [[Flockr]]s that need offline Profile visualization. Maybe useful also for applications.     * 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