1. 15 Oct, 2015 1 commit
  2. 18 Mar, 2015 1 commit
  3. 08 Jan, 2015 1 commit
  4. 11 Dec, 2014 1 commit
  5. 02 Dec, 2014 1 commit
  6. 29 Oct, 2014 2 commits
  7. 06 Oct, 2014 5 commits
  8. 19 Sep, 2014 1 commit
  9. 08 Sep, 2014 1 commit
  10. 26 Aug, 2014 1 commit
  11. 28 Jul, 2014 2 commits
  12. 18 Jul, 2014 1 commit
  13. 21 Jun, 2014 1 commit
    • antirez's avatar
      Client types generalized. · d97d1a64
      antirez authored
      Because of output buffer limits Redis internals had this idea of type of
      clients: normal, pubsub, slave. It is possible to set different output
      buffer limits for the three kinds of clients.
      
      However all the macros and API were named after output buffer limit
      classes, while the idea of a client type is a generic one that can be
      reused.
      
      This commit does two things:
      
      1) Rename the API and defines with more general names.
      2) Change the class of clients executing the MONITOR command from "slave"
         to "normal".
      
      "2" is a good idea because you want to have very special settings for
      slaves, that are not a good idea for MONITOR clients that are instead
      normal clients even if they are conceptually slave-alike (since it is a
      push protocol).
      
      The backward-compatibility breakage resulting from "2" is considered to
      be minimal to care, since MONITOR is a debugging command, and because
      anyway this change is not going to break the format or the behavior, but
      just when a connection is closed on big output buffer issues.
      d97d1a64
  14. 23 May, 2014 1 commit
  15. 23 Apr, 2014 1 commit
  16. 16 Apr, 2014 1 commit
  17. 21 Mar, 2014 2 commits
  18. 31 Jan, 2014 6 commits
  19. 19 Dec, 2013 3 commits
  20. 11 Dec, 2013 1 commit
  21. 06 Dec, 2013 1 commit
  22. 05 Dec, 2013 3 commits
  23. 09 Oct, 2013 1 commit
  24. 08 Jul, 2013 1 commit
    • antirez's avatar
      Revert "Document port6 and bind6 config options." · c76df730
      antirez authored
      IPv6 support is not going to use IPv6 specific options, just it will be
      possible to specify all the ipv4 / ipv6 addresses of the interfaces to
      bind, otherwise connections will be accepted from all the interfaces in
      both IPv4 and IPv6 addresses.
      
      This reverts commit 93570e17.
      c76df730