gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Slightly more efficient RM_ReplyWithEmptyString

Browse Source 
trimming talk about RESP protocol from API docs (should be independent to that anyway)
This commit is contained in:
Oran Agra 2019-11-14 09:46:46 +02:00
parent 73410c9d16
commit 10a834b48e
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/module.c
View File

@ -1389,7 +1389,7 @@ int RM_ReplyWithString(RedisModuleCtx *ctx, RedisModuleString *str) {
int RM_ReplyWithEmptyString(RedisModuleCtx *ctx) { int RM_ReplyWithEmptyString(RedisModuleCtx *ctx) {
client *c = moduleGetReplyClient(ctx); client *c = moduleGetReplyClient(ctx);
if (c == NULL) return REDISMODULE_OK; if (c == NULL) return REDISMODULE_OK;
addReplyBulkCBuffer(c, "", 0); addReply(c,shared.emptybulk);
return REDISMODULE_OK; return REDISMODULE_OK;
} }
@ -1404,8 +1404,7 @@ int RM_ReplyWithVerbatimString(RedisModuleCtx *ctx, const char *buf, size_t len)
return REDISMODULE_OK; return REDISMODULE_OK;
} }
/* Reply to the client with a NULL. In the RESP protocol a NULL is encoded /* Reply to the client with a NULL.
* as the string "$-1\r\n".
* *
* The function always returns REDISMODULE_OK. */ * The function always returns REDISMODULE_OK. */
int RM_ReplyWithNull(RedisModuleCtx *ctx) { int RM_ReplyWithNull(RedisModuleCtx *ctx) {