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 [2007/05/02 10:00] – * tvcutsem | start [2008/05/14 10:28] – * 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, our experimental | + | Welcome to our website on Ambient-Oriented Programming, a novel programming |
- | ===== What is AmbientTalk all about? ===== | + | {{: |
- | Ambient-Oriented programming | + | |
- | From this observation, | + | < |
- | * **Prototype-based** The mismatch between classes and distribution is well-documented and further aggravated in the context of mobile computing. | + | AmbientTalk |
- | * **Non-blocking** To avoid harming the autonomy of the mobile devices, no device should be blocked awaiting either to send a message or receive a result. | + | [[http:// |
- | * **Communication-Aware** To encompass network failures, objects should be able to keep a log of their own activities, allowing for error recovery. | + | </ |
- | * **Resource-Aware** Service discovery is an integral part of any ambient-oriented language since resources are encountered dynamically in the ever-changing network topology surrounding a device. | + | |
- | Check out the [[at: | + | ====== What is AmbientTalk |
- | ===== Contact ===== | + | 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. |
- | * The [[http://prog.vub.ac.be/mailman/listinfo/ambienttalk-user|AmbientTalk user list]], | + | From this observation, |
+ | * It employs a purely | ||
+ | * It abandons the RPC abstraction in favor of // | ||
+ | * It has built-in programming language constructs | ||
+ | * It features a dynamic OO kernel language built upon the principles | ||
- | ===== Further Reading ===== | + | Check out the [[at: |
- | **Ambient-Oriented Programming**, | + | AmbientTalk is not our only research artifact. There is also [[crime:introduction|CRIME]], a data-driven programming language which explores the logic programming paradigm to tackle similar coordination issues in mobile ad hoc networks. |
- | In " | + | |
- | **Ambient-Oriented Programming in AmbientTalk**, | + | ====== Contact ====== |
- | [ [[http:// | + | The [[http:// |
- | **Ambient-Oriented Programming**, | + | ====== Further Reading ====== |
- | [ [[http:// | + | |
+ | If you're interested in the Ambient-oriented Programming paradigm in general, check out the [[research: | ||
- | More information can also be found in the [[research: | + | If you're interested |
- | ===== Research Topics ===== | + | ====== Research Topics |
* [[research: | * [[research: | ||
* [[research: | * [[research: |
start.txt · Last modified: 2021/09/24 10:20 by elisag