Differences

This shows you the differences between two versions of the page.

--- start [2006/06/15 11:49] – Copied stijnm
+++ start [2006/07/01 18:56] – jdedecker
@@ Line 2: / Line 2: @@
 Welcome to our website on Ambient-Oriented Programming, an exciting new paradigm of computing geared towards promoting and programming spontaneous interactions between different mobile and/or embedded devices.
-This webpage is also the home of AmbientTalk, our experimental programming language to develop such applications. The current implementation of AmbientTalk is relatively stable and can be downloaded [[downloads|here]]. A tutorial on the language can be found [[tutorial:overview|here]].
+This webpage is also the home of AmbientTalk, our experimental programming language to develop such applications. The current implementation of AmbientTalk is relatively stable and can be downloaded [[at:Download|here]]. A tutorial on the language can be found [[at:Tutorial|here]].
 <note warning>
@@ Line 8: / Line 8: @@
 </note>
-===== So what is AmbientTalk all about? =====
+===== What is AmbientTalk all about? =====
-Ambient-Oriented programming is a programming <acronym title="A set of characteristics exhibited by all ambient-oriented programming languages">paradigm</acronym> 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 <acronym title="Every device acts as an independent computing unit">autonomous</acronym> nature of these devices as well as the <acronym title="Connections are broken as users move about">volatile connections</acronym> 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, several characteristics of programming languages can be derived. Informally we state that an ambient-oriented language is :
-* <span id="keyword">Prototype-based</span> The mismatch between classes and distribution is well-documented and further aggravated in the context of mobile computing.
+  * **Prototype-based** The mismatch between classes and distribution is well-documented and further aggravated in the context of mobile computing.
-* <span id="keyword">Non-blocking</span> To avoid harming the autonomy of the mobile devices, no device should be blocked awaiting either to send a message or receive a result.
+  * **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.
-* <span id="keyword">Communication-Aware</span> To encompass network failures, objects should be able to keep a log of their own activities, allowing for error recovery.
+  * **Communication-Aware** To encompass network failures, objects should be able to keep a log of their own activities, allowing for error recovery.
-* <span id="keyword">Resource-Aware</span> 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.
+  * **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.
-More information can be found in the [[research:papers|Papers]] section.
+==== Further Reading ====
+**Ambient-Oriented Programming**, Jessie Dedecker, Tom Van Cutsem, Stijn Mostinckx, Theo D'Hondt, Wolfgang De Meuter.
+In "OOPSLA '05: Companion of the 20th annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages and Applications. Pages 31-40. San Diego, U.S.A. ACM Press.", 2005 [ [[http://prog.vub.ac.be/Publications/2005/vub-prog-tr-05-10.pdf|download]] ]
+**Ambient-Oriented Programming in AmbientTalk**, Jessie Dedecker, Tom Van Cutsem, Stijn Mostinckx, Theo D'Hondt, Wolfgang De Meuter.  In "Proceedings of the 20th European Conference on Object-Oriented Programming (ECOOP), Dave Thomas (Ed.), Lecture Notes in Computer Science Vol. 4067, pp. 230-254, Springer-Verlag.", 2006
+More information can also be found in the [[research:papers|Papers]] section.
+===== Research Topics =====
+  * [[research:ambientrefs|Ambient References]]
+  * [[research:exceptions|Ambient-Oriented Exception Handling]]
+  * [[research:context|Role-Based Ambient Communications]]
+  * [[research:dgc|Distributed Garbage Collection]]
+===== Contact =====
+  * The AmbientTalk user list, for questions and general information on AmbientTalk: ''ambienttalk-user at prog.vub.ac.be''
+  * [[http://prog2.vub.ac.be:9006/JForum/forums/list.page|The AmbientTalk Forum]]