Exploiting Proximity in Event-Based Middleware for Collaborative Mobile Applications
Generate an AI Snapshot to get a quick, structured summary of this paper.
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
Middleware supporting event-based communication is widely recognized as being well suited to mobile applications since it naturally accommodates a dynamically changing population of interacting entities and the dynamic reconfiguration of the connections between them.
Abstract
Middleware supporting event-based communication is widely recognized as being well suited to mobile applications since it naturally accommodates a dynamically changing population of interacting entities and the dynamic reconfiguration of the connections between them. STEAM is an event-based middleware designed for use in ad hoc networks. STEAM differs from other event-based middleware in that its architecture does not rely on the presence of any separate infrastructure, event notification filters are distributed, and filtering may be applied to functional and non-functional attributes. In particular, filters may be applied to either the subject or the content of an event notification, or to non-functional attributes, such as location and time. Filters may be used to define geographical areas within which event notifications are valid, thereby bounding the propagation of these notifications. Such proximity-based filtering represents a natural way to filter events of interest in mobile applications. This paper describes the architecture and implementation of STEAM and its use of proximity-based filtering. In particular, we show how proximity-based filtering can be used to reduce the number of events delivered to collaborative mobile applications.
