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 [2008/08/26 19:28] – * tvcutsem | at:urbiflock [2010/08/04 17:34] – * elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock is a Facebook-like application framework | + | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: |
+ | |||
+ | Urbiflock is a Facebook-like application framework | ||
+ | |||
+ | Users can also build applications and plug them into the Urbiflock | ||
==== 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 | ||
- | ==== Modules | + | ==== Demo ==== |
- | * [[uf: | + | |
- | * [[uf: | + | < |
- | * [[uf: | + | <object width=" |
- | * [[uf: | + | </ |
- | * isNearby: physical proximity | + | |
- | * isFriend: static encoding of friendship relationships | + | ==== Target Platforms ==== |
- | * doesProfileMatch: | + | The Urbiflock framework has been written in the AmbientTalk language. As such, no configuration |
- | * combinators: | + | |
- | | + | AmbientTalk runs on a regular J2SE Java Virtual |
- | * [[uf: | + | Machine supporting version 1.3 or higher, Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC), and Android Platform version 1.6 or higher. |
- | * [[uf:application|Application]]: define the API of an " | + | |
+ | We have implemented a AWT UI interface for Urbiflock' | ||
+ | |||
+ | We are currently working on an Android UI interface for Urbiflock' | ||
+ | |||
+ | ==== Urbiflock architecture ==== | ||
+ | |||
+ | |||
+ | The architecture of the Urbiflock framework shown below is divided in three layers: applications, Urbiflock core, and Urbiflock infrastructure. | ||
+ | {{ :uf:urbiflock_architecture.png? | ||
- | A flock is defined | + | The application layer includes several core applications which are currently available in the framework such as flock and profile editors, and several users applications such as //I rate you// (IR8U), and // |
+ | The infrastructure layer consists | ||
- | === Predefined Flocks: === | + | In the rest of this subsection we list the relevant parts of the Urbiflock framework. |
- | * friend flockrs: isFriend | + | |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | ==== Architecture: ==== | + | * [[uf:flockr|Flockr]]: |
- | An ad hoc RETE-network: | + | * [[uf: |
- | Events are triggered by: | + | * [[uf: |
- | * discovery: joined(uid, | + | * [[uf:proximities|Characteristic Functions]]: |
- | * profile changes: changed(uid, | + | * [[uf:totam|TOTAM]]: |
- | * friend changes: friendAdded(uid, | + | * [[uf:application|Applications]]: |
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
- | 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. | ||
- | ==== TODO ==== | + | ==== Development |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | ==== Applications ==== | + | * [[uf: |
- | * [[uf:iflocku|IFlockU]]: a friend suggestor based on profile similarity and time spent in proximity. | + | * [[uf:Design|Whiteboard Design]] |
- | * [[uf:guanotes|Guanotes]]: a messenger | + | * [[:uf: |
+ | | ||
+ | | ||
+ | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag