- 11 Jul, 2012 1 commit
-
-
Alex Leverington authored
async: support for determining monitor mode, if so, repush replies callback in expectation of another reply.
-
- 11 Jul, 2011 1 commit
-
-
R. Tyler Croy authored
-
- 27 Jun, 2011 2 commits
-
-
Pieter Noordhuis authored
This commit adds a status argument to the connect callback. It will be called in the event of an unsuccessful connection as well, where the status argument is set to REDIS_ERR. It is set to REDIS_OK otherwise.
-
Pieter Noordhuis authored
-
- 18 Jun, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 29 May, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 24 May, 2011 2 commits
-
-
Blake Matheny authored
-
Blake Matheny authored
-
- 21 Apr, 2011 3 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 14 Jan, 2011 1 commit
-
-
Pieter Noordhuis authored
-
- 10 Jan, 2011 1 commit
-
-
Pierre Riteau authored
-
- 31 Dec, 2010 7 commits
-
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 29 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 28 Dec, 2010 5 commits
-
-
Pieter Noordhuis authored
-
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
-
Pieter Noordhuis authored
-
Pieter Noordhuis authored
-
- 16 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 07 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 01 Dec, 2010 1 commit
-
-
Pieter Noordhuis authored
This makes sure that the "data" field on the asynchronous context can be used for user-specific data.
-
- 15 Nov, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 03 Nov, 2010 1 commit
-
-
Pieter Noordhuis authored
-
- 02 Nov, 2010 1 commit
-
-
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.
-
- 01 Nov, 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
-