at:urbiflock
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2009/02/27 17:21] – tvcutsem | at:urbiflock [2009/11/18 13:45] – elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock is a Facebook-like application framework for mobile devices written in AmbientTalk. The framework takes care of managing a user's buddy lists, called | + | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: |
+ | |||
+ | Urbiflock is a Facebook-like application framework for mobile devices written in AmbientTalk. As in Facebook, users that join Urbiflock can meet other users and interact with them. For example users may broadcast announcements to each other, they can browse one another’s profile, launch interactive | ||
+ | polls, etc. The framework takes care of managing a user’s social networks, called | ||
+ | |||
+ | Similar to Facebook, users can build applications and plug them into the Urbiflock framework. Several core applications are currently available | ||
+ | The framework is currently still under development, | ||
==== Terminology ==== | ==== Terminology ==== | ||
- | * Flock: a group of proximate users | + | * Flockr: a user of the Urbiflock framework |
- | * Flockr: a user of the urbiflock framework | + | * Flock: a group of users |
* To flock: to become part of a group | * To flock: to become part of a group | ||
Line 32: | Line 38: | ||
WhiteBoard Drawings: | WhiteBoard Drawings: | ||
* [[uf: | * [[uf: | ||
- | |||
- | ==== Architecture ==== | ||
- | An ad hoc RETE-network. Events are triggered by: | ||
- | * discovery: '' | ||
- | * profile changes: '' | ||
- | * friend changes: '' | ||
- | |||
- | These events are received by the local flockr user object and propagated to all local proximities. Proximities translate these events into addUser / removeUser events to be processed by flocks. To process these events, flocks register themselves on their dependent proximity. | ||
==== Applications ==== | ==== Applications ==== |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag