From ef4acc82ca22ff52e1dbadd57b7eadc7d0883a2c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gr=C3=A9gory=20Wisniewski?= <gregory@nexedi.com>
Date: Mon, 8 Mar 2010 20:43:22 +0000
Subject: [PATCH] This TODO as no meaning since the timeout is at connection
 level.

git-svn-id: https://svn.erp5.org/repos/neo/trunk@1921 71dcc9de-d417-0410-9af5-da40c76e7ee4
---
 TODO | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/TODO b/TODO
index 24f37efa..bd3d1dea 100644
--- a/TODO
+++ b/TODO
@@ -34,10 +34,6 @@ RC  - Review output of pylint (CODE)
       involved nodes.
       It must be changed to a correspondance table using shorter keys (sent
       in the packet) to avoid repeating the same UUIDs many times.
-    - Make IdleEvent know what message they are expecting (DEBUGABILITY)
-      If a PING packet is sent, there is currently no way to know which
-      request created associated IdleEvent, nor which response is expected
-      (knowing either should be enough).
     - Consider using multicast for cluster-wide notifications. (BANDWITH)
       Currently, multi-receivers notifications are sent in unicast to each
       receiver. Multicast should be used.
-- 
2.30.9