User Tools

Site Tools


at:urbiflock

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
at:urbiflock [2010/08/04 17:56] – * elisagat:urbiflock [2010/10/19 19:28] – * 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//: an emerging type of applications that enable spontaneous interactions of people by means of handheld devices (such as their cell phones). These applications exploit the colocation of a number of mobile devices in the proximity to enable social interaction //on the move// UrbiFlock is a framework sculpted for the development of //pervasive social network applications//: an emerging type of applications that enable spontaneous interactions of people by means of handheld devices (such as their cell phones). These applications exploit the colocation of a number of mobile devices in the proximity to enable social interaction //on the move//
Line 9: Line 9:
 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 also counts with two user applications //I rate you (IR8U)// that allows users to ask proximate users to rate them on a certain subject, and //Guanotes// that allows user to send message to each other.   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 also counts with two user applications //I rate you (IR8U)// that allows users to ask proximate users to rate them on a certain subject, and //Guanotes// that allows user to send message to each other.  
  
-==== Terminology ====+===== Terminology =====
  
   * Flockr: a user of the Urbiflock framework   * Flockr: a user of the Urbiflock framework
Line 15: Line 15:
   * To flock: to become part of a group   * To flock: to become part of a group
  
-==== Demo ====+===== Demo =====
  
 <html> <html>
Line 21: Line 21:
 </html> </html>
  
-==== Target Platforms ====+===== 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.  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. 
  
Line 33: Line 33:
 The Urbiflock framework is available in the AmbientTalk distribution library under the frameworks/ folder. Visit  [[http://code.google.com/p/ambienttalk/|our google code repository]] to download the AmbientTalk distribution. The Urbiflock framework is available in the AmbientTalk distribution library under the frameworks/ folder. Visit  [[http://code.google.com/p/ambienttalk/|our google code repository]] to download the AmbientTalk distribution.
  
-==== Urbiflock architecture ====+===== The Urbiflock framework architecture =====
  
 The architecture of the Urbiflock framework shown below is divided in three layers: applications, Urbiflock core, and Urbiflock infrastructure.  The architecture of the Urbiflock framework shown below is divided in three layers: applications, Urbiflock core, and Urbiflock infrastructure. 
Line 59: Line 59:
 The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, and the service discovery and communication APIs to discover and communicate with nearby applications, respectively.  The infrastructure layer consists of three low-level abstractions on which the framework core is based: a RETE engine which orchestrates the flock composition, and the service discovery and communication APIs to discover and communicate with nearby applications, respectively. 
  
-==== Development ====+===== 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'Hondt. To appear in Mobile Computing and Applications Track at 26th Annual ACM Symposium on Applied Computing (SAC 2011), ACM, Taiwan, March 2011. ([[http://soft.vub.ac.be/Publications/2010/vub-tr-soft-10-20.pdf|pdf]])
  
-  * [[uf:todolist|Bugs and TODO List]] 
-  * [[uf:Design|Whiteboard Design]] 
-  * [[:uf:urbiflock_design.pdf| Design Diagram]] 
-  * To think about: 
-    * [[uf:persistence|Persistence]]: saving/loading framework and application data and prefs. 
-    * [[uf:privacy|Privacy]]: restrict access of applications to a user's flocks 
at/urbiflock.txt · Last modified: 2015/02/04 19:06 by elisag