research:posters
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
research:posters [2006/06/27 20:37] – tvcutsem | research:posters [2006/07/01 09:45] – jorge | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Posters ===== | + | ====== Posters |
This page provides an overview of the various posters related to [[research: | This page provides an overview of the various posters related to [[research: | ||
- | == Ambient References: Addressing Objects in Mobile Networks == | + | |
+ | === 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 | ||
+ | ============= | ||
+ | |||
+ | === Ambient References: Addressing Objects in Mobile Networks | ||
// | // | ||
Line 13: | Line 27: | ||
is significantly more difficult than in their fixed counterparts. | is significantly more difficult than in their fixed counterparts. | ||
This poster describes ambient references, a novel remote object referencing abstraction in the context of such mobile networks. Remote object references are one of the most fundamental programming abstractions of any distributed object-oriented programming language. The poster describes why novel referencing abstractions are needed and describes the benefits of ambient references over classic remote object references in mobile networks. | This poster describes ambient references, a novel remote object referencing abstraction in the context of such mobile networks. Remote object references are one of the most fundamental programming abstractions of any distributed object-oriented programming language. The poster describes why novel referencing abstractions are needed and describes the benefits of ambient references over classic remote object references in mobile networks. | ||
+ | |||
+ | **On display** at ECOOP 2006 | ||
+ | |||
+ | ============= | ||
+ | |||
+ | === 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 | ||
+ | |||
+ | ===== | ||
+ | |||
+ | |||
+ | === 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 | ||
+ | |||
+ | ===== | ||
+ | |||
+ | === 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 | **On display** at ECOOP 2006 | ||
===== | ===== |
research/posters.txt · Last modified: 2009/12/02 11:50 by alombide