- 16 Dec, 2010 1 commit
-
-
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 8 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
-
- 30 Oct, 2010 3 commits
-
-
Pieter Noordhuis authored
This allows users of the API to format a command without the need to have all the sds functions included, only for free'ing the returned wire-level command.
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 19 Oct, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 18 Oct, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 11 Oct, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
This removes the need to wrap an event_base pointer in the redisContext struct and allows multiple connections to be used in a single event_base. Also, use the *privdata argument to the provided callbacks to curry the redisEvent struct around.
-
- 10 Oct, 2010 1 commit
-
-
Nicolas Favre-Felix authored
-
- 07 Oct, 2010 2 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 25 Sep, 2010 4 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
Rather, use the return value REDIS_OK and REDIS_ERR to designate if calling a function has a successful outcome. When there was an error in performing the call the error field will be set inside the reader or the context.
-