Ambient-Oriented Programming

Each Flockr contains following info :

• Profile
• list of its Flocks where it is registered.
  • Note: maybe it should be stored in the profile.
• list of its Flocks.
  • predefined Flocks.
  • user-defined Flocks.

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 Flocks

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.

Not sure where to place: list of its friends Flockrs such that the Profile can be consulted offline. When a Flockr is connected for which there is a cached 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.