2e7d7cbabd
Proper support for RESP3 PUSH messages. By default, PUSH messages are now intercepted and the reply memory freed. This means existing code should work unchanged when connecting to Redis >= 6.0.0 even if `CLIENT TRACKING` were then enabled. Additionally, we define two callbacks users can configure if they wish to handle these messages in a custom way: void redisPushFn(void *privdata, void *reply); void redisAsyncPushFn(redisAsyncContext *ac, void *reply); See #825 |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| example-ae.c | ||
| example-glib.c | ||
| example-ivykis.c | ||
| example-libev.c | ||
| example-libevent-ssl.c | ||
| example-libevent.c | ||
| example-libuv.c | ||
| example-macosx.c | ||
| example-push.c | ||
| example-qt.cpp | ||
| example-qt.h | ||
| example-ssl.c | ||
| example.c | ||