- 21 Apr, 2011 9 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
-
- 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 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
This field is set in the read tasks that are passed to the reply object functions. This allows to curry arbitrary data to these functions.
-
- 19 Nov, 2010 1 commit
-
-
Ryan Tecco authored
-
- 04 Nov, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 03 Nov, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 02 Nov, 2010 4 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
When there is an I/O error, errno should be used to find out what is wrong. In other cases, errno cannot be used. So, use an explicit type in Hiredis to define the different error scenarios that can occur.
-
Pieter Noordhuis authored
-
- 01 Nov, 2010 3 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 31 Oct, 2010 4 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-