research:doforreal
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
research:doforreal [2010/08/04 13:55] – separately stijnm | research:doforreal [2010/08/04 14:25] – edited stijnm | ||
---|---|---|---|
Line 23: | Line 23: | ||
</ | </ | ||
- | While the //volatile data clouds// model considers RFID tags to be 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, |
- | Applications can interact | + | When interacting |
+ | the interaction with classic remote objects: | ||
- | When treating tags as objects, it is important | + | First of all, mobile RFID-enabled applications need a means to detect when a particular |
+ | mechanism to achieve this is to use the default [[at: | ||
- | 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. | + | 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. |
- | While messages are implicitly buffered during | + | By aligning tag objects with remote objects, one can develop mobile RFID-enabled applications without having to learn about a new concept. |
- | Within the tag object model, we have conducted initial experiments on how to use ad hoc // | + | A particularly interesting abstraction when developing mobile RFID-enabled applications are [[research: |
===== Comparison ===== | ===== Comparison ===== |
research/doforreal.txt · Last modified: 2010/08/04 17:34 by tvcutsem