Yichun Zhang

If you want to know if some kind of data has been pushed to server, you can just use the Redis pub/sub API: http://redis.io/topics/pubsub (for long polling) or do timed...

I don't have the time to implement recursive multi-bulk reply support in lua-resty-parser right now. You're welcome to submit a patch though :)

@toints I tried your example on my side and I got the following output with curl: ``` +OK +QUEUED +QUEUED *2 +OK :1 ``` It's not what you'd expect? If...

@toints The redis server receives the following raw redis query from nginx: ``` multi hmset 1463091589.721:header host localhost remote_addr 127.0.0.1 remote_port 55790 request_uri /redis_get status 000 sadd member:header 1463091589.721:/redis_get exec...

@toints Please provide a minimal and standalone example and exact steps that I can take to reproduce the "stress testing problem" on my side.

@liuguanglg Right, `ngx_redis2` does not really support Redis transactions. You may consider using the [lua-resty-redis](https://github.com/openresty/lua-resty-redis) library with the [ngx_lua](https://github.com/openresty/lua-nginx-module) module instead. Thank you for the report anyway :)

@vkozubal It's possible to do streaming post of large values into redis with a small buffer on the nginx side by using lua-nginx-module's downstream cosocket API and a modified version...

@vkozubal But not using this module. This module is hard to make the changes for your requirement. Since redis is a pure memory server, it might not be a good...

Hello! On Thu, Aug 16, 2012 at 11:06 AM, daurnimator [email protected] wrote: > The response seems to be valid; but I get an error: > > [error] 23868#0: *148 Redis...

Okay, now I get it. This is because the ngx_redis2 module cannot parse recursive redis multi-bulk replies and there is no quick way to add that. You're recommended to switch...