From 62aa5b27fd7c04aa84a7b09a02f18b12222601ea Mon Sep 17 00:00:00 2001
From: mquinson <mquinson@48e7efb5-ca39-0410-a469-dd3cf9ba447f>
Date: Fri, 31 Mar 2006 09:03:03 +0000
Subject: [PATCH] Those damn RPC are done now

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@2047 48e7efb5-ca39-0410-a469-dd3cf9ba447f
---
 TODO | 14 ++------------
 1 file changed, 2 insertions(+), 12 deletions(-)

diff --git a/TODO b/TODO
index f08caf0b4a..73e0bf13c4 100644
--- a/TODO
+++ b/TODO
@@ -167,18 +167,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
-- 
2.20.1