Add an entry in the TODO list about send ask() packets from the client thread

poll.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1109 71dcc9de-d417-0410-9af5-da40c76e7ee4

TODO

@@ -114,6 +114,9 @@ RC  - Review output of pylint (CODE)
     - Extend waitMessage to expect more than one response, on multiple connections (LATENCY)
       To be able to pipeline requests, waitMessage must be extended to allow responses to arrive out of order.
       The extreme case is when we must ask multiple nodes for object history (used to support undo) because different msg_ids are expected on different connections.
+    - Find a way to make ask() from the thread poll to allow send initial packet
+      (requestNodeIdentification) from the connectionCompleted() event instead
+      of app. This requires to know to what thread will wait for the answer.
 
   Later
     - Consider auto-generating cluster name upon initial startup (it might actualy be a partition property).