summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan-Erik Rediger <janerik@fnordig.de>2016-04-20 17:43:19 +0200
committerJan-Erik Rediger <janerik@fnordig.de>2016-04-20 17:49:20 +0200
commitb2213b764325163a1f2427b92e2f19ca437603eb (patch)
tree8ec7ae6640c5dc14ea596ce0902461efc5e67777
parent92d0e236611b841179d180e848c184d107f4a8be (diff)
docs: Note about thread-safety
-rw-r--r--README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.md b/README.md
index b40cdbb..104c110 100644
--- a/README.md
+++ b/README.md
@@ -58,6 +58,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
@@ -245,6 +247,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) {