X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/b96ca38c1b2f4ac542ae921e3645f78c640765fc..b0cb1eb2891892c2540d9169772498559d8033ba:/doc/doxygen/application.doc

diff --git a/doc/doxygen/application.doc b/doc/doxygen/application.doc
index d95ea26f00..af5fe1d399 100644
--- a/doc/doxygen/application.doc
+++ b/doc/doxygen/application.doc
@@ -1,28 +1,6 @@
 /** 
 @page application Describing your application
 
-TBD
-
-* Main concepts
-
-  - *Actor* (or process in legacy interfaces of SimGrid)
-  
-  - *Activities*: resource usage that applications do. This is what
-    takes time.
-    
-    Any given actor can do at most one foreground activity, while it
-    can also do several non-blocking activities in the background.
-    
-  - These activities take place on *Resources* (links, compute
-    machine, disks). Resources should be described (created) in the
-    Virtual Platform (link), but your application have many other ways
-    to interact with the resource.  
-
-  - The resources are arranged in a hierarchy of *Autonomous Systems*,
-    with which the application can also interact. The AS knows the
-    networking path between one resource to another.
-
-Speak of mailboxes here? Where if not?
 
 * Interfaces to describe applications
 
@@ -30,6 +8,9 @@ Speak of mailboxes here? Where if not?
 - Simple Legacy C interfaces: MSG and SimDag, with comparison.
 - Simple Java Interface: Currently MSG-based, but will be replaced with S4U stuff when ready
 - MPI applications
+- Event-oriented, and trace-based. The old documentation of the
+  obsolete MSG module was removed in
+  https://github.com/simgrid/simgrid/commit/e05361c201fb95d2b7605e59001cd0a49a489739
 
 - Arbitrary applications: Simterpose and Remote SimGrid (they are currently far from being usable).
 - State our goal of BYOS (build your own simulator), even if it's just a neat name for now