From: Salvatore Sanfilippo <antirez@gmail.com>
Date: Tue, 20 Sep 2011 09:12:14 +0000 (-0700)
Subject: Merge pull request #72 from datafueled/spelling
X-Git-Url: https://git.saurik.com/redis.git/commitdiff_plain/0ace6ce463695df1ff4c7ba848554f4c9b822f36?hp=-c

Merge pull request #72 from datafueled/spelling

Spelling fixes.
---

0ace6ce463695df1ff4c7ba848554f4c9b822f36
diff --combined TODO
index f24cec23,2e55cea7..1252ec68
--- a/TODO
+++ b/TODO
@@@ -17,14 -17,6 +17,14 @@@ API CHANGE
    the variable number of arguments represent values, and there is no conflict
    with the return value of the command.
  
 +2.6
 +===
 +
 +* Everything under the "SCRIPTING" section.
 +* Float increments (INCRBYFLOAT).
 +* Fix BRPOPLPUSH + vararg LPUSH semantics.
 +* AOF everysec fsync in background (either the aof-bg branch or something else).
 +
  CLUSTER
  =======
  
@@@ -42,13 -34,12 +42,13 @@@ SCRIPTIN
  * MULTI/EXEC/...: should we do more than simply ignoring it?
  * Prevent Lua from calling itself with redis("eval",...)
  * SCRIPT FLUSH or alike to start a fresh interpreter?
 -* http://redis.io/topics/sponsors
 +* Check better the replication handling.
 +* Prevent execution of writes if random commands are used.
  
  APPEND ONLY FILE
  ================
  
- * in AOF rewirte use HMSET to rewrite small hashes instead of multiple calls
+ * in AOF rewrite use HMSET to rewrite small hashes instead of multiple calls
    to HSET.
  
  OPTIMIZATIONS
@@@ -61,18 -52,42 +61,18 @@@
  * Redis big lists as linked lists of small ziplists?
    Possibly a simple heuristic that join near nodes when some node gets smaller than the low_level, and split it into two if gets bigger than high_level.
  
 -REPORTING
 -=========
 -
 -* Better INFO output with sections.
 -
  RANDOM
  ======
  
 +* Server should abort when getcwd() fails if there is some kind of persistence configured. Check this in the cron loop.
  * Clients should be closed as far as the output buffer list is bigger than a given number of elements (configurable in redis.conf)
  * Should the redis default configuration, and the default redis.conf, just bind 127.0.0.1?
  
  KNOWN BUGS
  ==========
  
 -* What happens in the following scenario:
 -    1) We are reading an AOF file.
 -    2) SETEX FOO 5 BAR
 -    3) APPEND FOO ZAP
 -    What happens if between 1 and 2 for some reason (system under huge load
 -    or alike) too many time passes? We should prevent expires while the
 -    AOF is loading.
  * #519: Slave may have expired keys that were never read in the master (so a DEL
    is not sent in the replication channel) but are already expired since
-   a lot of time. Maybe after a given delay that is undoubltly greater than
+   a lot of time. Maybe after a given delay that is undoubtably greater than
    the replication link latency we should expire this key on the slave on
    access?
 -
 -DISKSTORE TODO
 -==============
 -
 -* Fix FLUSHALL/FLUSHDB: the queue of pending reads/writes should be handled.
 -* Check that 00/00 and ff/ff exist at startup, otherwise exit with error.
 -* Implement sync flush option, where data is written synchronously on disk when a command is executed.
 -* Implement MULTI/EXEC as transaction abstract API to diskstore.c, with transaction_start, transaction_end, and a journal to recover.
 -* Stop BGSAVE thread on shutdown and any other condition where the child is killed during normal bgsave.
 -* Fix RANDOMKEY to really do something interesting
 -* Fix DBSIZE to really do something interesting
 -* Add a DEBUG command to check if an entry is or not in memory currently
 -* dscache.c near 236, kobj = createStringObject... we could use static obj.