research:posters
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
research:posters [2006/06/27 20:39] – *made tvcutsem | research:posters [2009/12/02 11:50] (current) – alombide | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Posters ====== | ====== Posters ====== | ||
- | This page provides an overview of the various posters related to [[research:amop|Ambient-Oriented Programming]]. A pdf version of each poster is available, together with a brief abstract describing it. | + | This page provides an overview of the various posters related to [[:start|Ambient-Oriented Programming]]. A pdf version of each poster is available, together with a brief abstract describing it. |
+ | |||
+ | |||
+ | === Ambient-Oriented Programming in AmbientTalk === | ||
+ | // | ||
+ | |||
+ | {{research: | ||
+ | **Abstract** Software development for mobile devices (such as smart phones and PDA’s) is given a new impetus with the advent of mobile networks. | ||
+ | equipped with wireless technology and are demarcated dynamically as users move about. | ||
+ | smart applications that can cooperate with their environment. Recently, this vision has been termed Ambient Intelligence (AmI for short) by the European Council' | ||
+ | Connections in mobile networks are volatile (because the communication range of the wireless technology is limited) and the network topology is open (because devices can appear and disappear unheraldedly). Developing application software for mobile networks still remains difficult because programming languages lack abstractions that deal with these mobile hardware characteristics. | ||
+ | potential network failures in the very heart of their basic computational steps. The poster ilustrates the design of the distributed programming language AmbientTalk, | ||
+ | |||
+ | **On display** at OOPSLA 2005, ECOOP 2006 | ||
+ | {{research: | ||
+ | |||
+ | ============= | ||
=== Ambient References: Addressing Objects in Mobile Networks === | === Ambient References: Addressing Objects in Mobile Networks === | ||
- | // | + | // |
- | [[research: | + | {{research: |
**Abstract** A significant body of research in ubiquitous computing deals with | **Abstract** A significant body of research in ubiquitous computing deals with | ||
mobile networks, i.e. networks of mobile devices interconnected | mobile networks, i.e. networks of mobile devices interconnected | ||
Line 15: | Line 31: | ||
**On display** at ECOOP 2006 | **On display** at ECOOP 2006 | ||
+ | {{research: | ||
+ | |||
+ | ============= | ||
+ | |||
+ | === Ambient-Oriented Exception Handling === | ||
+ | // | ||
+ | |||
+ | {{research: | ||
+ | **Abstract** Exception handling mechanisms are essential parts of current-day programming language because they provide a clean mechanism to separate the handling of exceptional events from default behaviour. In the context of mobile ad hoc networks, the increasing probability of exceptional events (such as disconnections, | ||
+ | |||
+ | **On display** at ECOOP 2006 | ||
+ | {{research: | ||
+ | |||
+ | ===== | ||
+ | |||
+ | |||
+ | === Semi-Automatic Garbage Collection for Mobile Networks === | ||
+ | // | ||
+ | |||
+ | {{research: | ||
+ | **Abstract** In the context of mobile networks, distributed garbage collection (DGC) must deal with volatile connections which may break remote references unexpectedly for an undetermined amount of time. This poster discusses the new challenges that mobile networks pose to DGC and describes a new approach called semi-automatic garbage collection to cope with them. The rationale behind semi-automatic garbage collection is that automatic transparent DGC is irreconcilable with such highly partial disconnected network topology. We propose to share the responsibility of DGC among collector and developer in such a way that the collector is steered by the developer who has semantic knowledge of the object graph. | ||
+ | |||
+ | **On display** at ECOOP 2006 | ||
+ | {{research: | ||
+ | |||
+ | ===== | ||
+ | |||
+ | === A Role-Based Implementation of Context-Dependent Communications Using Split Objects === | ||
+ | // | ||
+ | |||
+ | {{research: | ||
+ | **Abstract** This position paper focusses on the context-awareness feature in the domain of pervasive computing. Our particular interest is to investigate how context information may influence the communication between applications in this domain. We identify the problem of tangling context information with the definition of functional behaviour, and propose a solution based on a role-model to overcome this problem. | ||
+ | |||
+ | **On display** at ECOOP 2006 | ||
+ | {{research: | ||
+ | ===== | ||
+ | |||
+ | === Group Communication Abstractions for Distributed Reactive Systems === | ||
+ | // | ||
+ | |||
+ | {{research: | ||
+ | **Abstract** Pervasive computing in mobile ad hoc networks requires that applications react to a plethora of events fired by other devices in the mobile ad hoc network. Current context-aware and event-driven architectures require the programmer to react to these events via a carefully crafted network of observers and event handlers, around which the whole application is structured. The object oriented, distributed and concurrent language AmbientTalk offers Reactive Programming as an alternative paradigm to be able to write such pervasive applications while retaining a conventional programming style. However, due to the asynchronous communication between remote objects, event handlers are still required to capture and process results computed in parallel. We show that, by exploiting the Reactive Programming mechanisms and the first class messages offered by AmbientTalk, | ||
+ | |||
+ | **On display** at ECOOP 2008 | ||
+ | {{research: | ||
===== | ===== |
research/posters.txt · Last modified: 2009/12/02 11:50 by alombide