Ruby client updated

[redis.git] / TODO

diff --git a/TODO b/TODO
index 0e1083d97b341a091714907ad4be1b2c37577e47..7040af2c1f318776410eb2e9838ffadbcc0b1755 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,11 +1,18 @@
+BEFORE REDIS 1.0.0-rc1
+
+- Remove max number of args limit

 - GETSET
 - GETSET

-- keys expire
-- sunion ssub
+- Fix pure-PHP lib version 4 for the new protocol
+- persistent expires

 - network layer stresser in test in demo
 - maxclients directive
 - check 'server.dirty' everywere
 - replication automated tests
 - network layer stresser in test in demo
 - maxclients directive
 - check 'server.dirty' everywere
 - replication automated tests

+- replication non stopping master<->slave syncronization

 - an external tool able to perform the 'difference' between two Redis servers. It's like 'diff', but against Redis servers, and the output is the set of commands needed to turn the first server into the second, suitable to be sent via netcat.
 - an external tool able to perform the 'difference' between two Redis servers. It's like 'diff', but against Redis servers, and the output is the set of commands needed to turn the first server into the second, suitable to be sent via netcat.

+- Shutdown must kill other background savings before to start saving. Otherwise the DB can get replaced by the child that rename(2) after the parent for some reason.
+- Add missing commands in documentation
+- Document replication

 
    $ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
    $ cat diff.txt | nc 192.168.1.1 6379
 
    $ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
    $ cat diff.txt | nc 192.168.1.1 6379


@@ -14,4 +21,8 @@
 
 This command should be smart and don't use too much memory, that is, take two connections at the same time against the two servers and perform the comparison key by key. Probably the initial "KEYS *" is unavoidable.
 
 
 This command should be smart and don't use too much memory, that is, take two connections at the same time against the two servers and perform the comparison key by key. Probably the initial "KEYS *" is unavoidable.
 

-- objects sharing, "objectsharing yes", "objectsharingpool 1024"
+- objects sharing configuration, add the directive "objectsharingpool <size>"
+
+FUTURE HINTS
+
+- if in-memory values compression will be implemented, make sure to implement this so that addReply() is able to handle compressed objects, just creating an uncompressed version on the fly and adding this to the output queue instead of the original one. When insetad we need to look at the object string value (SORT BY for example), call a function that will turn the object into an uncompresed one.