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/11/18 13:37] – updating elisag | at:urbiflock [2010/10/20 18:42] – adding elisag | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Urbiflock ====== | ====== Urbiflock ====== | ||
- | ==== What is Urbiflock? ==== | + | ===== What is Urbiflock? |
UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: | UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: | ||
- | Urbiflock is a Facebook-like application framework for mobile devices | + | 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), |
- | 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), | + | |
- | Similar to Facebook, users can build applications and plug them into the Urbiflock framework. Several core applications are currently available in the Urbiflock framework, such as flock creators and profile viewers, and also users applications | + | Users can also build applications and plug them into the Urbiflock framework. Several core applications are currently available in the Urbiflock framework, such as flock creators and profile viewers. The framework |
- | 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 | ||
- | ==== Modules | + | ===== Demo ===== |
- | * [[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 to ' | + | < |
+ | <object width=" | ||
+ | </ | ||
- | Predefined Flocks: | + | ===== Target Platforms ===== |
- | * friend flockrs: isFriend | + | |
- | * nearby flockrs: isNearby | + | |
- | * nearby friend flockrs: isFriend & isNearby | + | |
- | WhiteBoard Drawings: | + | 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. |
- | * [[uf: | + | |
- | ==== Architecture ==== | + | AmbientTalk runs on a regular J2SE Java Virtual |
- | An ad hoc RETE-network. Events are triggered by: | + | Machine supporting version 1.3 or higher, Java 2 micro edition |
- | * 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 | + | We have implemented a AWT UI interface for Urbiflock' |
- | ==== Applications ==== | + | {{:uf:urbiflockonx10.jpg? |
- | * [[uf:viewer|Flock Viewer]]: a viewer and editor to view existing flocks and to create new flocks. | + | |
- | * [[uf:app_viewer|Application Viewer]]: a viewer and editor to view existing applications and install/ | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | * [[uf: | + | |
- | ==== Target Platforms ==== | + | We are currently |
- | * UrbiFlock will work on any computer which has java installed. | + | |
- | * We are currently | + | |
- | ==== Development ==== | + | The Urbiflock framework is available in the AmbientTalk distribution library under the frameworks/ folder. Visit [[http:// |
- | * [[uf:todolist|Bugs and TODO List]] | + | |
- | ==== To think about ==== | + | ===== The Urbiflock framework architecture ===== |
- | * [[uf:persistence|Persistence]]: saving/loading | + | |
- | * [[uf:privacy|Privacy]]: restrict access of applications to a user's flocks | + | The architecture of the Urbiflock framework shown below is divided in three layers: applications, |
+ | {{ : | ||
+ | |||
+ | The application layer includes the API of an " | ||
+ | | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | There are also several user applications in the framework: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | * [[uf: | ||
+ | |||
+ | The Urbiflock' | ||
+ | |||
+ | * [[uf:flockr|Flockr]]: A flockr represents a user in the framework. A flockr is also the gateway that other applications | ||
+ | * [[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' |
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag