[Neo-report] r1865 gregory - /trunk/TODO

[nobody at svn.erp5.org]

Author: gregory
Date: Fri Feb 26 14:04:08 2010
New Revision: 1865

Log:
Revert a misunderstood TODO entry.

This is not fixed, IdleEvent is not associated to the packet that create it.

Modified:
    trunk/TODO

Modified: trunk/TODO
==============================================================================
--- trunk/TODO [iso-8859-1] (original)
+++ trunk/TODO [iso-8859-1] Fri Feb 26 14:04:08 2010
@@ -34,6 +34,10 @@
       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.