Commit 5953febf authored by Grégory Wisniewski's avatar Grégory Wisniewski

Move TODO items from README file and fix NEO Storage class name.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1137 71dcc9de-d417-0410-9af5-da40c76e7ee4
parent 1fb45279
...@@ -2,27 +2,6 @@ This is the second prototype of NEO. The design is described in: ...@@ -2,27 +2,6 @@ This is the second prototype of NEO. The design is described in:
http://www.nexedi.org/workspaces/neo http://www.nexedi.org/workspaces/neo
TODO
- Handling connection timeouts.
- Handling write timeouts.
- IdleEvent for a certain message type as well as a message ID.
- Flushing write buffers only without reading packets.
- Garbage collection of unused nodes.
- Stopping packet processing by returning a boolean value from
a handler, otherwise too tricky to exchange a handler with another.
- History.
- Multiple undo.
- Expiration of temporariry down nodes.
Requirements Requirements
- Python 2.4 or later - Python 2.4 or later
...@@ -63,6 +42,7 @@ Installation ...@@ -63,6 +42,7 @@ Installation
b. Just create the storage object and play with it: b. Just create the storage object and play with it:
from neo.client.NEOStorare import NEOStorage from neo.client.Storare import Storage
s = NEOStorage(master_addr="127.0.0.1", master_port=10010, name="main") s = Storage(master_nodes="127.0.0.1:10010", name="main",
connector="SocketConnector")
... ...
...@@ -152,3 +152,18 @@ RC - Review output of pylint (CODE) ...@@ -152,3 +152,18 @@ RC - Review output of pylint (CODE)
may cause a big network overhead. It would be better to refuse any client 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 connection and thus no OID allocation during import. It may be interesting
to create a new stage for the cluster startup... to be discussed. to create a new stage for the cluster startup... to be discussed.
Old TODO
- Handling connection timeouts.
- Handling write timeouts.
- IdleEvent for a certain message type as well as a message ID.
- Flushing write buffers only without reading packets.
- Garbage collection of unused nodes.
- Stopping packet processing by returning a boolean value from
a handler, otherwise too tricky to exchange a handler with another.
- History.
- Multiple undo.
- Expiration of temporarily down nodes.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment