3 - Resize the expires hash tables if needed as well
4 - Elapsed time in logs for SAVE when saving is going to take more than 2 seconds
5 - TTL command that returns -1 if a key is not volatile otherwise the time to live of a volatile key.
6 - Remove max number of args limit
7 - What happens if the saving child gets killed or segfaults instead of ending normally? Handle this.
8 - Make sinterstore / unionstore / sdiffstore returning the cardinality of the resulting set.
10 - check 'server.dirty' everywere
11 - replication automated tests
12 - 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.
13 - Document replication
14 - Objects sharing configuration, add the directive "objectsharingpool <size>"
15 - Make sure to convert all the fstat() calls to 64bit versions.
16 - SINTERCOUNT, SUNIONCOUNT, SDIFFCOUNT
18 AFTER 1.0 stable release
20 - Use partial qsort for SORT + LIMIT
25 - In memory compression: 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.