diff options
author | not-a-robot <not-a-robot@rediger.net> | 2016-04-20 18:31:34 +0200 |
---|---|---|
committer | not-a-robot <not-a-robot@rediger.net> | 2016-04-20 18:31:34 +0200 |
commit | 81e8176bacd27e2cc0db021a22c03a2891ade7eb (patch) | |
tree | 26e230b31bd4897a766f89a4b40a899b9fb46924 | |
parent | 35a16d6f69aed97efd8ae3542a72e44c5f9ecaee (diff) | |
parent | b2213b764325163a1f2427b92e2f19ca437603eb (diff) |
Auto merge of #417 - redis:thread-safety, r=badboy
docs: Note about thread-safety
-rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -68,6 +68,8 @@ if (c == NULL || c->err) { } ``` +*Note: A `redisContext` is not thread-safe.* + ### Sending commands There are several ways to issue commands to Redis. The first that will be introduced is @@ -255,6 +257,9 @@ Redis. It returns a pointer to the newly created `redisAsyncContext` struct. The should be checked after creation to see if there were errors creating the connection. Because the connection that will be created is non-blocking, the kernel is not able to instantly return if the specified host and port is able to accept a connection. + +*Note: A `redisAsyncContext` is not thread-safe.* + ```c redisAsyncContext *c = redisAsyncConnect("127.0.0.1", 6379); if (c->err) { |