Except during import, no OID overlapping should happen. Remove TODO entries

about this issue and add another about data import improvements.


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

TODO

@@ -117,14 +117,6 @@ RC Known bugs
     - Fix primary master node reconnection
       It happens that, once disconnected from primary master node, admin node becomes unable to re-establish the connection.
       Make admin not re-ask partition table on reconnection to primary master.
-    Master
-    - It should broadcast to storage and client the last OID generated to allow
-    them dectect OID overlapping.
-    Storage
-    - The storage must detect when a client store a object with a greater OID
-    than the last generated by the master node. It should at least notice to
-    restart the whole cluster to avoid conflicts. This is mainly the case when
-    importing data.
 
   Later
     - Consider auto-generating cluster name upon initial startup (it might actualy be a partition property).
@@ -133,3 +125,9 @@ RC Known bugs
     - Decentralize primary master tasks as much as possible (consider distributed lock mechanisms, ...)
     - Make admin node able to monitor multiple clusters simultaneously
     - Choose how to compute the storage size
+    - When importing data, objects with non-allocated OIDs are stored. The
+    storage can detect this and could notify the master to not allocatexd lower
+    OIDs. But during import, each object stored trigger this notification and
+    may cause a big network overhead. It would be better to refuse any client 
+    connection and thus no OID allocation during import. It may be interesting 
+    to create a new stage for the cluster startup... to be discussed.