at:urbiflock
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
at:urbiflock [2008/08/26 19:25] – created tvcutsem | at:urbiflock [2009/11/18 15:14] – elisag | ||
---|---|---|---|
Line 3: | Line 3: | ||
==== What is Urbiflock? ==== | ==== What is Urbiflock? ==== | ||
- | Urbiflock | + | UrbiFlock |
- | ==== Modules ==== | + | Urbiflock is a Facebook-like application framework for mobile devices written in AmbientTalk. As in Facebook, |
- | * [[uf: | + | polls, etc. The framework takes care of managing |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * isNearby: physical proximity | + | |
- | * isFriend: static encoding of friendship relationships | + | |
- | * doesProfileMatch: | + | |
- | * combinators: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | A flock is defined as a list of references | + | Similar |
- | === Predefined Flocks: | + | ==== Terminology ==== |
- | * friend flockrs: isFriend | + | |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | ==== Architecture: ==== | + | * Flockr: a user of the Urbiflock framework |
- | An ad hoc RETE-network: | + | * Flock: a group of users |
+ | * To flock: to become part of a group | ||
- | Events are triggered by: | + | ==== Urbiflock architecture ==== |
- | * discovery: joined(uid, | + | |
- | * profile changes: changed(uid, | + | |
- | * friend changes: friendAdded(uid, | + | |
- | 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 ==== | + | The architecture |
- | * Persistence | + | {{ : |
- | * Privacy: restrict access | + | |
- | ==== Applications ==== | + | 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 // |
- | * [[uf: | + | The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, |
- | * [[uf: | + | |
+ | In the rest of this subsection we list the relevant parts of the Urbiflock framework. | ||
+ | |||
+ | | ||
+ | * [[uf: | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | ==== Target Platforms ==== | ||
+ | Rather than building a platform-independent framework, our aim is to assist in the rapid development of pervasive social networking applications. The Urbiflock framework has been entirely written in the AmbientTalk language. As such, no configuration is required to be able to quickly script new applications on it once AmbientTalk is running on the target platform. | ||
+ | |||
+ | AmbientTalk requires a regular J2SE Java Virtual | ||
+ | Machine supporting version 1.3 or higher. The implementation also runs on the Java 2 micro edition (J2ME) platform, under the connected device configuration (CDC). | ||
+ | |||
+ | We have done some test to deploy our framework on HTC touch cruise pda's. In order to configure your HTC Touch device for our framework you can follow the instruction [[private: | ||
+ | |||
+ | We are currently working on deploying our framework on HTC Hero, a phone running on the Android platform. | ||
+ | |||
+ | ==== Development ==== | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[: | ||
+ | * To think about: | ||
+ | * [[uf: | ||
+ | * [[uf: |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag