4 WARNING: are you a possible Redis contributor?
 
   5          Before implementing what is listed what is listed in this file
 
   6          please drop a message in the Redis google group or chat with
 
   7          antirez or pietern on irc.freenode.org #redis to check if the work
 
   8          is already in progress and if the feature is still interesting for
 
   9          us, and *how* exactly this can be implemented to have good changes
 
  10          of a merge. Otherwise it is probably wasted work! Thank you
 
  15 * Check that 00/00 and ff/ff exist at startup, otherwise exit with error.
 
  16 * Implement sync flush option, where data is written synchronously on disk when a command is executed.
 
  17 * Implement MULTI/EXEC as transaction abstract API to diskstore.c, with transaction_start, transaction_end, and a journal to recover.
 
  22 * PING between master and slave from time to time, so we can subject the
 
  23 master-slave link to timeout, and detect when the connection is gone even
 
  24 if the socket is still up.
 
  29 * SORT: Don't copy the list into a vector when BY argument is constant.
 
  30 * Write the hash table size of every db in the dump, so that Redis can resize the hash table just one time when loading a big DB.
 
  31 * Read-only mode for slaves.
 
  36 * What happens in the following scenario:
 
  37     1) We are reading an AOF file.
 
  40     What happens if between 1 and 2 for some reason (system under huge load
 
  41     or alike) too many time passes? We should prevent expires while the