Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
hiredis
Commits
b455b338
Commit
b455b338
authored
Apr 22, 2022
by
Yossi Gottlieb
Browse files
Handle push notifications before or after reply.
parent
d7683f35
Changes
1
Hide whitespace changes
Inline
Side-by-side
test.c
View file @
b455b338
...
...
@@ -914,6 +914,11 @@ static void test_resp3_push_handler(redisContext *c) {
old
=
redisSetPushCallback
(
c
,
push_handler
);
test
(
"We can set a custom RESP3 PUSH handler: "
);
reply
=
redisCommand
(
c
,
"SET key:0 val:0"
);
/* We need another command because depending on the version of Redis, the
* notification may be delivered after the command's reply. */
test_cond
(
reply
!=
NULL
);
freeReplyObject
(
reply
);
reply
=
redisCommand
(
c
,
"PING"
);
test_cond
(
reply
!=
NULL
&&
reply
->
type
==
REDIS_REPLY_STATUS
&&
pc
.
str
==
1
);
freeReplyObject
(
reply
);
...
...
@@ -929,6 +934,12 @@ static void test_resp3_push_handler(redisContext *c) {
assert
((
reply
=
redisCommand
(
c
,
"GET key:0"
))
!=
NULL
);
freeReplyObject
(
reply
);
assert
((
reply
=
redisCommand
(
c
,
"SET key:0 invalid"
))
!=
NULL
);
/* Depending on Redis version, we may receive either push notification or
* status reply. Both cases are valid. */
if
(
reply
->
type
==
REDIS_REPLY_STATUS
)
{
freeReplyObject
(
reply
);
reply
=
redisCommand
(
c
,
"PING"
);
}
test_cond
(
reply
->
type
==
REDIS_REPLY_PUSH
);
freeReplyObject
(
reply
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment