Ruby client updated

[redis.git] / TODO

diff --git a/TODO b/TODO
index 85304b96a2f7c11bb1333cf30aa934fd83fafed3..7040af2c1f318776410eb2e9838ffadbcc0b1755 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,14 +1,18 @@
-- Protocol changes as discussed in the Redis group
-- keys expire
-- sunion ssub
-- write integers in a special way on disk, use the unused 11|.... length.
-- 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 automated tests
-- a command, or an external tool, to perform the SHA1SUM of the whole dataset, so that if the dataset between two servers is identical, so will be the MD5SUM
+- 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
 
    $ ./redis-diff 192.168.1.1 192.168.1.2 > diff.txt
    $ cat diff.txt | nc 192.168.1.1 6379
@@ -17,6 +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.
 
-- objects sharing, "objectsharing yes", "objectsharingpool 1024"
+- objects sharing configuration, add the directive "objectsharingpool <size>"
+
+FUTURE HINTS
 
-* Include Lua and Perl bindings
+- 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.