start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
start [2006/06/27 10:39] – tvcutsem | start [2007/08/01 08:57] – changed tvcutsem | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Welcome to Ambient-Oriented Programming ====== | + | ~~NOTOC~~ |
- | Welcome to our website on Ambient-Oriented Programming, | + | |
- | This webpage is also the home of AmbientTalk, | + | ====== Ambient-Oriented Programming ====== |
+ | Welcome to our website on Ambient-Oriented Programming, | ||
- | <note warning> | + | {{: |
- | This webpage is under construction! | + | |
- | </ | + | ===== What is AmbientTalk about? ===== |
- | ===== So what is AmbientTalk all about? ===== | ||
Ambient-Oriented programming is a programming paradigm whose properties are derived from the characteristics of hardware platforms for mobile computing. Mobile hardware devices are often provided with wireless networks facilities, allowing them to engage in collaboration with their environment. However, the autonomous nature of these devices as well as the volatile connections over their wireless infrastructure has its repercussions on the software that employs them. The basic assumption of the Ambient-Oriented Programming paradigm is that languages should incorporate possible network failures at the heart of their programming model. | Ambient-Oriented programming is a programming paradigm whose properties are derived from the characteristics of hardware platforms for mobile computing. Mobile hardware devices are often provided with wireless networks facilities, allowing them to engage in collaboration with their environment. However, the autonomous nature of these devices as well as the volatile connections over their wireless infrastructure has its repercussions on the software that employs them. The basic assumption of the Ambient-Oriented Programming paradigm is that languages should incorporate possible network failures at the heart of their programming model. | ||
- | From this observation, | + | From this observation, |
- | * **Prototype-based** The mismatch between classes and distribution | + | * It employs a purely //event-driven// concurrency framework, founded on actors. |
- | * **Non-blocking** To avoid harming | + | |
- | * **Communication-Aware** To encompass network failures, objects should | + | * It has built-in programming language constructs for objects to // |
- | * **Resource-Aware** Service discovery is an integral part of any ambient-oriented | + | * It features a dynamic OO kernel language built upon the principles |
+ | |||
+ | Check out the [[at: | ||
+ | |||
+ | AmbientTalk is not our only research artifact. There is also [[crime: | ||
+ | |||
+ | ===== Contact ===== | ||
+ | The [[http:// | ||
+ | |||
+ | ===== Further Reading ===== | ||
+ | |||
+ | If you're interested in the Ambient-oriented | ||
+ | |||
+ | If you're interested in the AmbientTalk programming language, check out the [[research: | ||
- | More information can be found in the [[research: | + | More information can also be found in the [[research: |
===== Research Topics ===== | ===== Research Topics ===== | ||
* [[research: | * [[research: | ||
+ | * [[research: | ||
+ | * [[research: | ||
+ | * [[research: | ||
+ | * [[research: | ||
+ | * [[research: |
start.txt · Last modified: 2021/09/24 10:20 by elisag