- 11 Jul, 2013 1 commit
-
-
Noah Williamsson authored
The struct timeval argument in redisConnectWithTimeout(), redisConnectUnixWithTimeout(), redisSetTimeout(), redisContextSetTimeout(), redisContextConnectTcp() and redisContextConnectUnix() is never modified and can therefore be marked as const. Signed-off-by:
Noah Williamsson <noah.williamsson@gmail.com>
-
- 29 Apr, 2013 1 commit
-
-
Allen.Dou authored
Make Connection KeepAlive being optional instead of default.
-
- 19 Apr, 2013 1 commit
-
-
Allen.Dou authored
Keep client alive even though no command was sent to server for a long time.
-
- 28 Aug, 2012 1 commit
-
-
Pieter Noordhuis authored
-
- 21 Aug, 2012 2 commits
-
-
antirez authored
Hiredis can handle multi bulk replies with a fixed (hardcoded) level of nesting. This should be changed in the future in order to avoid hardcoded limits. As a quick fix this commit moves the max nesting from 2 to 7, so that there are no problems when processing replies from the SLOWLOG command, from Redis Sentinel, or generated by Redis Lua Scripts (that are allowed to generate replies with any level of nesting).
-
antirez authored
Hiredis used to free unused redisReader buffers bigger than 16k. Now this limit is configurable (see the documentation updated by this commit) in order to allow working with big payloads without incurring to speed penalty.
-
- 11 Jul, 2012 1 commit
-
-
Alex Leverington authored
async: support for determining monitor mode, if so, repush replies callback in expectation of another reply.
-
- 02 Dec, 2011 1 commit
-
-
mrb authored
-
- 19 Jun, 2011 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
This reverts commit 77540aa3. The change in buffer strategy is too large to put in a minor release. It is put in a separate branch in the meantime, so it can be refined and released together with a minor version bump.
-
- 05 May, 2011 1 commit
-
-
Pieter Noordhuis authored
This is done by only truncating the read buffer once a full reply has been read. The buffer is no longer truncated halfway through reading a reply. In addition: pass offset/length of protocol and content via the read tasks.
-
- 22 Apr, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 21 Apr, 2011 14 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 20 Apr, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 04 Feb, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 27 Jan, 2011 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 07 Jan, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 31 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 28 Dec, 2010 2 commits
-
-
Pieter Noordhuis authored
To make sure that these functions can also be called from functions other than command callbacks, the flag IN_CALLBACK is introduced that holds whether the context is currently executing a callback. If so, redisAsyncFree() and redisAsyncDisconnect() should delegate their task to the reply processor to avoid segfaults.
-
Pieter Noordhuis authored
-
- 16 Dec, 2010 3 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
When no reply object functions are defined, the reply type integer is returned from redisGetReply(). This sets the *reply argument to the consumed reply, where 0 means that it was not possible to consume a full reply. With REDIS_REPLY_ERROR having the same value, there is no way to tell the difference between an error reply and not consuming a reply.
-
- 26 Nov, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 24 Nov, 2010 1 commit
-
-
Pieter Noordhuis authored
-