X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/810976b1e41f58871360b39fec33f2a472e4d358..3ac9e81ace9b9a129314e7e5e489dcdf583547da:/TODO

diff --git a/TODO b/TODO
index f08caf0b4a..bd0098bf1f 100644
--- a/TODO
+++ b/TODO
@@ -17,6 +17,8 @@ xbt/log.h:/** \name WARN
 xbt/log.h:/** \name ERROR
 xbt/log.h:/** \name CRITICAL
 
+gras_socket_close should be blocking until all the data sent have been
+received by the other side (implemented with an ACK mechanism).
 
 ###
 ### Planned
@@ -63,7 +65,9 @@ xbt/log.h:/** \name CRITICAL
 
 [modules]
   * better formalisation of what modules are (amok deeply needs it)
-    configuration + init() + exit() + dependencies
+    configuration + init() + join() + exit() + leave() + dependencies
+    init and exit are run only once
+    join and leave are run for each process.
   * allow to load them at runtime
     check in erlang how they upgrade them without downtime
 
@@ -167,18 +171,8 @@ xbt/log.h:/** \name CRITICAL
   * gras_datadesc_import_nws?
 
 [Messaging]
-  * A proper RPC mecanism
-    - gras_rpctype_declare_v (name,ver, payload_request, payload_answer)
-      (or gras_msgtype_declare_rpc_v). 
-    - Attaching a cb works the same way.
-    - gras_msg_rpc(peer, &request, &answer)
-    - On the wire, a byte indicate the message type:
-      - 0: one-way message (what we have for now)
-      - 1: method call (answer expected; sessionID attached)
-      - 2: successful return (usual datatype attached, with sessionID)
-      - 3: error return (payload = exception)
-      - other message types are possible (forwarding request, group
-        communication)
+  * Other message types than oneway & RPC are possible:
+     - forwarding request, group communication
   * Message priority
   * Message forwarding
   * Group communication