This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
research:doforreal [2010/08/04 12:29] stijnm small |
research:doforreal [2010/08/04 14:36] stijnm Minor |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Distributed Objects for Real ====== | ====== Distributed Objects for Real ====== | ||
- | In the past few years, researchers at the Software Languages Lab have performed a number of experiments to discover how to facilitate the development of so-called __Mo__bile | + | Over the past year, a number of researchers at the Software Languages Lab have been involved in experiments |
- | __R__FID-__ena__bled (Morena) | + | |
- | Over the past year, we have developed | + | During these experiments, we have approached the development of such applications from two opposing |
- | == Volatile Data Clouds == | + | ===== Volatile Data Clouds ===== |
+ | < | ||
The //volatile data clouds// model considers RFID tags to be data containers whose presence or absence can be used to steer the application. | The //volatile data clouds// model considers RFID tags to be data containers whose presence or absence can be used to steer the application. | ||
Line 12: | Line 12: | ||
Since the collection is implicitly tied to the environment and changes frequently in response to events emitted by the RFID reader, //change// is at the very heart of the model. | Since the collection is implicitly tied to the environment and changes frequently in response to events emitted by the RFID reader, //change// is at the very heart of the model. | ||
- | When programing with reactive values that represent | + | Concretely, |
- | Furthermore, | + | Another important aspect is efficiently detecting |
+ | occurrences, we make use of [[research: | ||
- | Most importantly, | + | ===== Tags Objects ===== |
- | == Tags Objects == | + | < |
+ | The tag objects model represents RFID tags as full-blown objects, which introduces a natural mechanism to deal with **mutable tag data**. | ||
+ | </ | ||
- | While the //volatile data clouds// model considers RFID tags as containers of data which is to be filtered and interpreted by the application, | + | While the //volatile data clouds// model considers RFID tags to be containers of data which is to be filtered and interpreted by the application, |
- | When treating tags as objects, | + | When interacting with these tag objects, |
+ | the interaction with classic remote | ||
- | Once a tag object has been discovered, the application can start to interact with it. However, if either the user of the application or the tagged object is roaming, it is extremely likely that the tag will (temporarily) go out of range. | + | First of all, mobile RFID-enabled applications need a means to detect |
+ | mechanism to achieve this is to use the default [[at: | ||
- | While messages are implicitly buffered during | + | Once a tag object has been discovered, the application can start to interact with it. However, if either the user of the application or the tagged object |
- | Within the tag object model, we have conducted initial experiments on how to use ad hoc // | + | By aligning |
- | == Comparison == | + | A particularly interesting abstraction when developing mobile RFID-enabled applications are [[research: |
- | Having implemented both models, it remains unclear whether one of the models presented in this paper is to be preferred over the other. | + | ===== Comparison ===== |
- | The volatile data clouds model treats RFID tags as simple containers of data and aims at providing applications with expressive means to represent a collection of nearby tags which is constantly in flux. | + | Having implemented both models, we have found their virtues |
- | The tag objects model on the other hand treats the contents of an RFID tag as a full-fledged object. | + | The volatile data clouds model treats RFID tags as simple containers of data and aims at providing applications with expressive means to represent a collection of nearby tags which is constantly in flux. Consequently, |
+ | |||
+ | The tag objects model on the other hand treats the contents of an RFID tag as a full-fledged object. | ||
In all likelihood, a programming model that fully leverages the advantages of a world teeming with tagged objects will incorporate elements of both models presented here. | In all likelihood, a programming model that fully leverages the advantages of a world teeming with tagged objects will incorporate elements of both models presented here. | ||
- | == Further Reading == | + | ===== Further Reading |
* Distributed Objects for Real. Stijn Mostinckx, Andoni Lombide Carreton, Kevin Pinte, Wolfgang De Meuter. Technical report, 2010, Vrije Universiteit Brussel [[|pdf]] | * Distributed Objects for Real. Stijn Mostinckx, Andoni Lombide Carreton, Kevin Pinte, Wolfgang De Meuter. Technical report, 2010, Vrije Universiteit Brussel [[|pdf]] |