Reactive Queries in Mobile Ad Hoc Networks

Andoni Lombide Carreton, Tom Van Cutsem, Wolfgang De Meuter

Research output: Chapter in Book/Report/Conference proceedingConference paper

Abstract

Pervasive computing in mobile ad hoc networks requires that applications query their network environment for services and react to a plethora of events fired by other devices in that network responding to such queries. 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, while inherently introducing complex concurrency issues. This paper proposes the integration of two techniques to solve these problems: ambient references and reactive programming. Ambient references are object-oriented communication abstractions that represent nearby remote objects in the mobile network and that make it possible to generate the events mentioned above. The reactive programming paradigm provides an abstraction over events such that the application can be written in a conventional programming style with explicit control flow.
Original languageEnglish
Title of host publicationProceedings of the 6th international workshop on Middleware for pervasive and ad-hoc computing
EditorsSotirios Terzis
PublisherACM
Pages13-18
Number of pages6
ISBN (Print)978-1-60558-364-8
Publication statusPublished - 2 Dec 2008
EventFinds and Results from the Swedish Cyprus Expedition: A Gender Perspective at the Medelhavsmuseet - Stockholm, Sweden
Duration: 21 Sep 200925 Sep 2009

Publication series

NameACM International Conference Proceedings Series

Conference

ConferenceFinds and Results from the Swedish Cyprus Expedition: A Gender Perspective at the Medelhavsmuseet
Country/TerritorySweden
CityStockholm
Period21/09/0925/09/09

Bibliographical note

Sotirios Terzis

Keywords

  • Mobile ad hoc networks
  • Event-driven systems
  • AmbientTalk

Fingerprint

Dive into the research topics of 'Reactive Queries in Mobile Ad Hoc Networks'. Together they form a unique fingerprint.

Cite this