Differences

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

--- start [2007/07/28 17:26] – added tvcutsem
+++ start [2007/08/01 08:57] – changed tvcutsem
@@ Line 14: / Line 14: @@
   * It abandons the RPC abstraction in favor of //asynchronous, non-blocking// message passing. Because the system automatically buffers such messages while the receiver of the message is disconnected, the programmer can abstract over temporary network failures //by default//!
   * It has built-in programming language constructs for objects to //discover// one another in the local ad hoc network. Peer-to-peer //service discovery// is built into the language.
-  * It features a dynamic OO kernel language built upon the principles of prototype-based programmer. More importantly, the kernel language is reflective and hence extensible from within the language itself.
+  * It features a dynamic OO kernel language built upon the principles of prototype-based programming. More importantly, the kernel language is reflective and hence extensible from within the language itself.
 Check out the [[at:introduction|introduction]] to AmbientTalk for a hands-on example showing you the benefits in actual code.
+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.
 ===== Contact =====
+The [[http://prog.vub.ac.be/mailman/listinfo/ambienttalk-user|AmbientTalk user list]], for questions and general information on AmbientTalk: ''ambienttalk-user at prog.vub.ac.be''. If you want to contact any one of us personally, please see the [[people|People pages]] for personal contact details.
-  * The [[http://prog.vub.ac.be/mailman/listinfo/ambienttalk-user|AmbientTalk user list]], for questions and general information on AmbientTalk: ''ambienttalk-user at prog.vub.ac.be''. If you want to contact any one of us personally, please see the [[people|People]] pages for personal contact details.
 ===== Further Reading =====
-**Ambient-Oriented Programming**, Jessie Dedecker, Tom Van Cutsem, Stijn Mostinckx, Theo D'Hondt, Wolfgang De Meuter.
+If you're interested in the Ambient-oriented Programming paradigm in general, check out the [[research:papers|papers on AmOP]] page. The seminal OOPSLA2005 Onward! paper pretty much sums up our earliest musings on AmOP. A year later, at ECOOP2006, we refined these ideas and applied them to our first AmbientTalk prototype.
-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
-[ [[http://prog.vub.ac.be/Publications/2006/vub-prog-tr-06-11.pdf|download]] ]
-**Ambient-Oriented Programming**, Jessie Dedecker, Ph.D. Thesis, Vrije Universiteit Brussel.
-[ [[http://prog.vub.ac.be/Publications/2006/vub-prog-phd-06-01.pdf|download]] ]
+If you're interested in the AmbientTalk programming language, check out the [[research:atpapers|papers on AmbientTalk]] page. The ECOOP2006 paper is the first paper describing AmbientTalk in-depth. However, since mid-2006, the language has been extensively revised. A good starting point for reading about the revised language is the SCCC2007 paper.
 More information can also be found in the [[research:papers|Papers]] section.