[![Build Status](https://travis-ci.org/redis/hiredis.png)](https://travis-ci.org/redis/hiredis)
# HIREDIS
Hiredis is a minimalistic C client library for the [Redis](http://redis.io/) database.
It is minimalistic because it just adds minimal support for the protocol, but
at the same time it uses an high level printf-alike API in order to make it
much higher level than otherwise suggested by its minimal code base and the
lack of explicit bindings for every Redis command.
Apart from supporting sending commands and receiving replies, it comes with
a reply parser that is decoupled from the I/O layer. It
is a stream parser designed for easy reusability, which can for instance be used
in higher level language bindings for efficient reply parsing.
Hiredis only supports the binary-safe Redis protocol, so you can use it with any
Redis version >= 1.2.0.
The library comes with multiple APIs. There is the
*synchronous API*, the *asynchronous API* and the *reply parsing API*.
## UPGRADING
Version 0.9.0 is a major overhaul of hiredis in every aspect. However, upgrading existing
code using hiredis should not be a big pain. The key thing to keep in mind when
upgrading is that hiredis >= 0.9.0 uses a `redisContext*` to keep state, in contrast to
the stateless 0.0.1 that only has a file descriptor to work with.
## Synchronous API
To consume the synchronous API, there are only a few function calls that need to be introduced:
redisContext *redisConnect(const char *ip, int port);
void *redisCommand(redisContext *c, const char *format, ...);
void freeReplyObject(void *reply);
### Connecting
The function `redisConnect` is used to create a so-called `redisContext`. The
context is where Hiredis holds state for a connection. The `redisContext`
struct has an integer `err` field that is non-zero when an the connection is in
an error state. The field `errstr` will contain a string with a description of
the error. More information on errors can be found in the **Errors** section.
After trying to connect to Redis using `redisConnect` you should
check the `err` field to see if establishing the connection was successful:
redisContext *c = redisConnect("127.0.0.1", 6379);
if (c != NULL && c->err) {
printf("Error: %s\n", c->errstr);
// handle error
}
### Sending commands
There are several ways to issue commands to Redis. The first that will be introduced is
`redisCommand`. This function takes a format similar to printf. In the simplest form,
it is used like this:
reply = redisCommand(context, "SET foo bar");
The specifier `%s` interpolates a string in the command, and uses `strlen` to
determine the length of the string:
reply = redisCommand(context, "SET foo %s", value);
When you need to pass binary safe strings in a command, the `%b` specifier can be
used. Together with a pointer to the string, it requires a `size_t` length argument
of the string:
reply = redisCommand(context, "SET foo %b", value, (size_t) valuelen);
Internally, Hiredis splits the command in different arguments and will
convert it to the protocol used to communicate with Redis.
One or more spaces separates arguments, so you can use the specifiers
anywhere in an argument:
reply = redisCommand(context, "SET key:%s %s", myid, value);
### Using replies
The return value of `redisCommand` holds a reply when the command was
successfully executed. When an error occurs, the return value is `NULL` and
the `err` field in the context will be set (see section on **Errors**).
Once an error is returned the context cannot be reused and you should set up
a new connection.
The standard replies that `redisCommand` are of the type `redisReply`. The
`type` field in the `redisReply` should be used to test what kind of reply
was received:
* **`REDIS_REPLY_STATUS`**:
* The command replied with a status reply. The status string can be accessed using `reply->str`.
The length of this string can be accessed using `reply->len`.
* **`REDIS_REPLY_ERROR`**:
* The command replied with an error. The error string can be accessed identical to `REDIS_REPLY_STATUS`.
* **`REDIS_REPLY_INTEGER`**:
* The command replied with an integer. The integer value can be accessed using the
`reply->integer` field of type `long long`.
* **`REDIS_REPLY_NIL`**:
* The command replied with a **nil** object. There is no data to access.
* **`REDIS_REPLY_STRING`**:
* A bulk (string) reply. The value of the reply can be accessed using `reply->str`.
The length of this string can be accessed using `reply->len`.
* **`REDIS_REPLY_ARRAY`**:
* A multi bulk reply. The number of elements in the multi bulk reply is stored in
`reply->elements`. Every element in the multi bulk reply is a `redisReply` object as well
and can be accessed via `reply->element[..index..]`.
Redis may reply with nested arrays but this is fully supported.
Replies should be freed using the `freeReplyObject()` function.
Note that this function will take care of freeing sub-replies objects
contained in arrays and nested arrays, so there is no need for the user to
free the sub replies (it is actually harmful and will corrupt the memory).
**Important:** the current version of hiredis (0.10.0) free's replies when the
asynchronous API is used. This means you should not call `freeReplyObject` when
you use this API. The reply is cleaned up by hiredis _after_ the callback
returns. This behavior will probably change in future releases, so make sure to
keep an eye on the changelog when upgrading (see issue #39).
### Cleaning up
To disconnect and free the context the following function can be used:
void redisFree(redisContext *c);
This function immediately closes the socket and then free's the allocations done in
creating the context.
### Sending commands (cont'd)
Together with `redisCommand`, the function `redisCommandArgv` can be used to issue commands.
It has the following prototype:
void *redisCommandArgv(redisContext *c, int argc, const char **argv, const size_t *argvlen);
It takes the number of arguments `argc`, an array of strings `argv` and the lengths of the
arguments `argvlen`. For convenience, `argvlen` may be set to `NULL` and the function will
use `strlen(3)` on every argument to determine its length. Obviously, when any of the arguments
need to be binary safe, the entire array of lengths `argvlen` should be provided.
The return value has the same semantic as `redisCommand`.
### Pipelining
To explain how Hiredis supports pipelining in a blocking connection, there needs to be
understanding of the internal execution flow.
When any of the functions in the `redisCommand` family is called, Hiredis first formats the
command according to the Redis protocol. The formatted command is then put in the output buffer
of the context. This output buffer is dynamic, so it can hold any number of commands.
After the command is put in the output buffer, `redisGetReply` is called. This function has the
following two execution paths:
1. The input buffer is non-empty:
* Try to parse a single reply from the input buffer and return it
* If no reply could be parsed, continue at *2*
2. The input buffer is empty:
* Write the **entire** output buffer to the socket
* Read from the socket until a single reply could be parsed
The function `redisGetReply` is exported as part of the Hiredis API and can be used when a reply
is expected on the socket. To pipeline commands, the only things that needs to be done is
filling up the output buffer. For this cause, two commands can be used that are identical
to the `redisCommand` family, apart from not returning a reply:
void redisAppendCommand(redisContext *c, const char *format, ...);
void redisAppendCommandArgv(redisContext *c, int argc, const char **argv, const size_t *argvlen);
After calling either function one or more times, `redisGetReply` can be used to receive the
subsequent replies. The return value
没有合适的资源?快使用搜索试试~ 我知道了~
Linux 版Redis3.0
需积分: 0 8 下载量 68 浏览量
2017-09-18
22:11:11
上传
评论
收藏 1.3MB GZ 举报
温馨提示
共512个文件
c:176个
h:120个
tcl:79个
linux 版redis 源码安装,3.0版本与2.0相比良好的支持redis集群,安装过程中可能执行gem install redis /usr/local/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- redis (LoadError) from /usr/local/lib/ruby/2.3.0/rubygems/core_ext/kernel_ require.rb:55:in `require' from src/redis-trib.rb:25:in `<main>'出现错误,缺少redis-3.2.1.gem,如需下载点击http://download.csdn.net/download/baidu_36342103/9982383
资源推荐
资源详情
资源评论
收起资源包目录
Linux 版Redis3.0 (512个子文件)
00-RELEASENOTES 28KB
lua.1 4KB
luac.1 4KB
jemalloc.3 54KB
configure.ac 46KB
luavs.bat 1KB
BUGS 53B
cluster.c 195KB
sentinel.c 150KB
redis.c 144KB
t_zset.c 94KB
SFMT.c 89KB
replication.c 83KB
config.c 82KB
redis-cli.c 74KB
arena.c 72KB
networking.c 62KB
aof.c 59KB
hyperloglog.c 56KB
rdb.c 55KB
ziplist.c 52KB
jemalloc.c 49KB
ctl.c 46KB
scripting.c 42KB
lua_cjson.c 41KB
t_list.c 40KB
db.c 39KB
hiredis.c 37KB
dict.c 36KB
lparser.c 36KB
linenoise.c 35KB
debug.c 35KB
sds.c 34KB
sds.c 34KB
t_set.c 32KB
prof.c 31KB
lua_cmsgpack.c 30KB
redis-benchmark.c 28KB
latency.c 26KB
test.c 25KB
t_hash.c 24KB
object.c 23KB
lstrlib.c 23KB
lvm.c 23KB
lapi.c 22KB
bitops.c 22KB
async.c 22KB
redis-check-dump.c 22KB
sort.c 21KB
util.c 21KB
lcode.c 21KB
SFMT.c 20KB
lgc.c 20KB
anet.c 19KB
loadlib.c 19KB
math.c 18KB
lauxlib.c 17KB
lbaselib.c 17KB
stats.c 17KB
ldebug.c 16KB
zipmap.c 16KB
ltable.c 16KB
intset.c 16KB
ae.c 15KB
t_string.c 15KB
ldo.c 15KB
util.c 14KB
ckh.c 14KB
liolib.c 13KB
pubsub.c 13KB
tcache.c 13KB
llex.c 12KB
mallctl.c 12KB
net.c 12KB
rio.c 12KB
stats.c 11KB
multi.c 11KB
chunk.c 11KB
lua_struct.c 11KB
ae_evport.c 11KB
zmalloc.c 11KB
crc64.c 10KB
dict.c 10KB
lua.c 10KB
ldblib.c 10KB
adlist.c 10KB
memtest.c 9KB
bio.c 9KB
lzf_c.c 9KB
util.c 8KB
huge.c 8KB
blocked.c 7KB
rb.c 7KB
ltablib.c 7KB
sha1.c 7KB
zone.c 7KB
slowlog.c 7KB
sparkline.c 6KB
redis-check-aof.c 6KB
strbuf.c 6KB
共 512 条
- 1
- 2
- 3
- 4
- 5
- 6
资源评论
倒走人生
- 粉丝: 5
- 资源: 5
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功