This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
research:recap [2010/07/31 17:08] stijnm Brief |
research:recap [2010/07/31 18:23] stijnm added |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ~~NOTOC~~ | ||
- | ===== Reactive Context-Aware Programming ===== | ||
- | [[http:// | ||
- | < | ||
- | This page is under construction, | ||
- | </ | ||
- | |||
- | Reactive Context-Aware Programming (ReCAP) extends the ambient-oriented programming paradigm to tailor it for the Internet of Things (IoT): a network environment in which physical objects are given an embedded digital representation. | ||
- | |||
- | This enables IoT applications to detect the proximity and/or availability of physical objects and use this information to provide context-sentive services and information. | ||
- | |||
- | ==== Causally Connected Applications ==== | ||
- | † Quick-link: [[research: | ||
- | |||
- | IoT applications are //causally connected// to their environment; | ||
- | |||
- | Reacting to changes in the environment requires registering one or more event handlers. | ||
- | |||
- | The use of such event handlers introduces an //inversion of control//, where the control flow of the application is scattered across a number of event handlers. | ||
- | additional event handlers to propagate environmental changes to modules which are only indirectly affected by them. | ||
- | |||
- | Note that it is often possible to avoid the inversion of control altogether. | ||
- | |||
- | ==== Window on the World ==== |