summaryrefslogtreecommitdiff
path: root/hiredis.h
AgeCommit message (Collapse)Author
2012-08-27Bump minor version because reader struct changedPieter Noordhuis
2012-08-21Max depth of multi-bulk reply moved from 2 to 7.antirez
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).
2012-08-21Configurable reader max idle buffer size.antirez
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.
2012-07-11async: support for determining monitor mode, if so, repush replies callback ↵Alex Leverington
in expectation of another reply.
2011-12-02increase read depth by one, would allow ruby redis client to read from slowlogmrb
2011-06-19Bump patch versionPieter Noordhuis
2011-06-19Revert "Add function to retrieve formatted reply"Pieter Noordhuis
This reverts commit 77540aa31694aa1e14d41f60a0452e49a2fed86a. 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.
2011-05-05Add function to retrieve formatted replyPieter Noordhuis
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.
2011-04-22Bump version to 0.10.0Pieter Noordhuis
2011-04-21Update licensePieter Noordhuis
2011-04-21Handle OOM when doing blocking requestsPieter Noordhuis
2011-04-21More OOM checks in the protocol readerPieter Noordhuis
2011-04-21Rename *ReplyReader* to *Reader*Pieter Noordhuis
2011-04-21Use static buffer for error string on contextPieter Noordhuis
2011-04-21Create protocol reader when creating contextPieter Noordhuis
2011-04-21Move prototypes around in headerPieter Noordhuis
2011-04-21Reply object functions can be set by the user after creating the readerPieter Noordhuis
2011-04-21Privdata can be set directly on the structPieter Noordhuis
2011-04-21Remove useless castsPieter Noordhuis
2011-04-21Remove accessor functions now the redisReader struct is publicPieter Noordhuis
2011-04-21Move definitions aroundPieter Noordhuis
2011-04-21Forward declaration is not necessaryPieter Noordhuis
2011-04-21Make redisReader struct publicPieter Noordhuis
2011-04-20Use pre-allocated buffer for error strings in readerPieter Noordhuis
2011-02-04Use select(2) for enforce a timeout on blocking connect(2)Pieter Noordhuis
2011-01-27redisReplyReaderFeed should take a const char*Pieter Noordhuis
2011-01-27Avoid warnings with -Wstrict-prototypesPieter Noordhuis
2011-01-07Return error on socket timeout for a blocking contextPieter Noordhuis
2010-12-31Change reply processing code to prepare for pub/subPieter Noordhuis
2010-12-28Fix the async free() and disconnect() functionsPieter Noordhuis
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.
2010-12-28Add function to explicitly free an async contextPieter Noordhuis
2010-12-16Bump versionPieter Noordhuis
2010-12-16Add myself to license in some filesPieter Noordhuis
2010-12-16Redefine REDIS_REPLY_ERROR to be non-zeroPieter Noordhuis
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.
2010-11-26Bump versionPieter Noordhuis
2010-11-26Rename 'parent' field in read tasks to 'obj'Pieter Noordhuis
2010-11-24Add pointer to parent task in read tasksPieter Noordhuis
2010-11-24Add privdata field to reply readerPieter Noordhuis
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.
2010-11-19add extern "C" for C++ compilesRyan Tecco
2010-11-04The buffer length to feed should be a size_tPieter Noordhuis
2010-11-04Return the reply type when the reply object function set is NULLPieter Noordhuis
2010-11-03Add version information to hiredis.hPieter Noordhuis
2010-11-03Allow to connect using a unix socket from hiredisPieter Noordhuis
2010-11-03Expose redisGetReplyFromReader as public APIPieter Noordhuis
2010-11-02Strip net.c down to the bare minimumPieter Noordhuis
2010-11-02Change error reporting to have an explicit typePieter Noordhuis
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.
2010-11-02Remove superfluous definitionPieter Noordhuis
2010-11-01There is no longer need for a separate redisDisconnectPieter Noordhuis
2010-11-01Strip non-blocking callbacks from hiredis.cPieter Noordhuis
2010-11-01Add support to lazily disconnect an asynchronous connectionPieter Noordhuis