RANDOMKEY issue 26 fixed, generic test + regression added

[redis.git] / TODO

diff --git a/TODO b/TODO
index 7d91a10331937c9a4b39e5006113e8c77c599a12..7040af2c1f318776410eb2e9838ffadbcc0b1755 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,36 +1,28 @@
-BETA 8 TODO
-- keys expire
-- sunion ssub
-- write integers in a special way on disk (and on memory?)
-- compact types for disk storing of short strings (no 4 bytes overhead!)
+BEFORE REDIS 1.0.0-rc1
+
+- Remove max number of args limit
+- GETSET
+- 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 tests
-- command line client. If the last argument of a bulk command is missing get it from stdin. Example:
-    $ echo "bar" | redis-client SET foo
-    $ redis-client SET foo bar
-    $ redis-client GET foo
-    bar
-    $
-- Make Redis aware of the memory it is using thanks to getrusage() and report this info with the INFO command.
-- INFO command: clients, slave/master, requests/second in the last N seconds, memory usage, uptime, dirty, lastsave
-
-FUTURE
-
-ROLLBACK command:
+- 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.
+- 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
 
-    ROLLBACK UNSET x
-    SET x 10
-    EXPIRE x 3600
-    COMMIT
+   $ ./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
+   $ # No output now the servers are identical
 
-    (multiple rollbacks are allowed)
+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.
 
-    or alternatively
+- objects sharing configuration, add the directive "objectsharingpool <size>"
 
-    TRANSACTION SET x 1000
-    TRANSACTION EXPIRE x 1000
-    COMMIT
+FUTURE HINTS
 
-    but this sucks since there is no way to check the error message.
+- 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.