1. 11 Jul, 2013 1 commit
    • Geoff Garside's avatar
      Use getaddrinfo(3) in anetResolve. #apichange · 855ff8df
      Geoff Garside authored
      Change anetResolve() function to use getaddrinfo(3) to resolve hostnames.
      Resolved hostnames are limited to those reachable by the AF_INET address
      family.
      
      API Change: anetResolve requires additional argument.
        additional argument required to specify the length of the character
        buffer the IP address is written to in order to comply with
        inet_ntop(3) function semantics. inet_ntop(3) replaces inet_ntoa(3)
        as it has been designed to be compatible with more address families.
      855ff8df
  2. 08 Jul, 2013 7 commits
  3. 03 Jul, 2013 2 commits
    • antirez's avatar
      redis-cli: introduced --pipe-timeout. · 3e350126
      antirez authored
      When in --pipe mode, after all the data transfer to the server is
      complete, now redis-cli waits at max the specified amount of
      seconds (30 by default, use 0 to wait forever) without receiving any
      reply at all from the server. After this time limit the operation is
      aborted with an error.
      
      That's related to issue #681.
      3e350126
    • antirez's avatar
      redis-cli --pipe: send final ECHO in a safer way. · 24b37992
      antirez authored
      If the protocol read from stdin happened to contain grabage (invalid
      random chars), in the previous implementation it was possible to end
      with something like:
      
      dksfjdksjflskfjl*2\r\n$4\r\nECHO....
      
      That is invalid as the *2 should start into a new line. Now we prefix
      the ECHO with a CRLF that has no effects on the server but prevents this
      issues most of the times.
      
      Of course if the offending wrong sequence is something like:
      
      $3248772349\r\n
      
      No one is going to save us as Redis will wait for data in the context of
      a big argument, so this fix does not cover all the cases.
      
      This partially fixes issue #681.
      24b37992
  4. 02 Jul, 2013 5 commits
  5. 01 Jul, 2013 2 commits
  6. 27 Jun, 2013 1 commit
  7. 26 Jun, 2013 21 commits
  8. 20 Jun, 2013 1 commit