d8ff72387d
We need to allow our users to use redisContext->privdata as context for any RESP3 PUSH messages, which means we can't use it for managing SSL connections. Bulletpoints: * Create a secondary redisContext member for internal use only called privctx and rename the redisContextFuncs->free_privdata accordingly. * Adds a `free_privdata` function pointer so the user can tie allocated memory to the lifetime of a redisContext (like they can already do with redisAsyncContext) * Enables SSL tests in .travis.yml |
||
|---|---|---|
| .. | ||
| 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 | ||