Yichun Zhang

@rshriram Well, the shm zone API is generic, but it has to be exposed and get utilized by different nginx subsystems, for obvious reasons. Regarding code duplication, well, nginx prefers...

@alonbg I'm not sure about the details at this point, unfortunately. But you're more than welcome to fiddle about with various different options in your own branches and send us...

@webandbusiness You should paste the exact error messages you are getting. Otherwise we cannot guess out what problems you may have. Also, give the following preview version a try: https://openresty.org/download/openresty-1.15.8.1rc0.tar.gz

@zhiquy It's not yet ported to the stream subsystem but should be easy: https://github.com/openresty/lua-resty-core/blob/master/lib/ngx/ocsp.lua Will you create a pull request for it?

@brg-liuwei Seems like your branch fails the Travis CI testing: https://travis-ci.org/openresty/stream-lua-nginx-module/builds/156263654 And also see below in this ticket's web UI. Your branch does not even compile. Will you fix that...

@doujiang24 @cuiweixie @yangshuxin Will you have a look at this for me? Many thanks!

@brg-liuwei I suggest adding this feature to ngx_http_lua_module first since we usually sync changes in only one direction (i.e., from `ngx_http_lua` to `ngx_stream_lua`), not both :)

I think we are going for the `receive_any()` route now? @spacewander What's your plan please?

@xiaohuilam Because literal values specified directly in nginx.conf are all strings per se. That is, `32` is exactly equivalent to `"32"` to the nginx config file parser. We could add...

@alonbg BTW, the Travis CI testing is broken on this PR, as evidenced below.