This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
at:urbiflock [2008/08/26 19:25] tvcutsem created |
at:urbiflock [2015/02/04 19:06] (current) elisag |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | ==== What is Urbiflock? ==== | ||
- | Urbiflock is a Facebook-like application framework written in AmbientTalk. The framework takes care of managing a user's buddy lists, called " | + | ===== Scripting Mobile Social Applications ===== |
- | ==== Modules ==== | + | The recent profusion |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * isNearby: | + | |
- | * isFriend: static encoding | + | |
- | * doesProfileMatch: | + | |
- | * combinators: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | A flock is defined as a list of references to ' | + | In this work we propose Urbiflock, |
- | === Predefined Flocks: | + | ===== What is Urbiflock? ===== |
- | * friend flockrs: isFriend | + | |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | ==== Architecture: | + | Urbiflock is a Facebook-like application framework for mobile devices. 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 “flocks”. A flock represents a loosely-defined group of users. A flock can be compared to a Facebook group (for example, a group of your old classmates), |
- | An ad hoc RETE-network: | + | |
- | Events | + | Users can also build applications and plug them into the Urbiflock framework. Several core applications |
- | * discovery: joined(uid,flockr) | + | |
- | * profile changes: changed(uid,flockr, | + | |
- | * 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. | + | ===== Terminology ===== |
- | ==== TODO ==== | + | * Flockr: a user of the Urbiflock framework |
- | * Persistence | + | * Flock: a group of users |
- | * Privacy: restrict access of applications | + | * To flock: to become part of a group |
- | ==== Applications | + | ===== Demo ===== |
- | * [[uf: | + | |
- | * [[uf:guanotes|Guanotes]]: a messenger application | + | < |
+ | <object width=" | ||
+ | </ | ||
+ | |||
+ | ===== Target Platforms ===== | ||
+ | |||
+ | The Urbiflock framework has been 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 runs on a regular J2SE Java Virtual | ||
+ | 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. | ||
+ | |||
+ | We have implemented a AWT UI interface for Urbiflock' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | We are currently working on an Android UI interface for Urbiflock' | ||
+ | |||
+ | The Urbiflock framework is available in the AmbientTalk distribution library under the frameworks/ folder. Visit [[http:// | ||
+ | |||
+ | ===== The Urbiflock framework architecture ===== | ||
+ | |||
+ | The architecture of the Urbiflock framework shown below is divided in three layers: applications, | ||
+ | {{ : | ||
+ | |||
+ | The application layer includes the API of an " | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | There are also several user applications in the framework: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | | ||
+ | |||
+ | The Urbiflock' | ||
+ | |||
+ | * [[uf:flockr|Flockr]]: A flockr represents | ||
+ | * [[uf: | ||
+ | |||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[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, | ||
+ | |||
+ | ===== Further Reading ===== | ||
+ | |||
+ | **Flocks: Enabling Dynamic Group Interactions in Mobile Social Networking Applications**. E. Gonzalez Boix, A. Lombide Carreton, C. Scholliers, T. Van Cutsem, W. De Meuter, T. D' |