Hello!
On Tue, May 31, 2016 at 4:28 PM, Lord Nynex wrote:
> Yes! As of last I heard from agentzh this is planned. The primary issue
> right now is the way the stream_by_lua API is implemented. Currently, it
> duplicates some code in a way that is probably best to rethink. I believe
> there is a long term plan to augment this API in such a way that it can
> become more ubiquitous across stream and http blocks.
>
Yes, there will be an ngx_meta_lua_module to avoid code duplication :)
Well, there is another issue with nginx core's stream subsystem on how
the access handler is implemented. The module ctx arrays are
initialized *after* the stream access handler is called, which is a
show stopper. We should contact the nginx team to correct this in the
nginx core.
Another issue is that unlike the http subsystem, the stream access
handler is not composable. That is, only one nginx module can register
the access handler for any stream server. This is also annoying and
should get changed in the nginx core.
But yes, access_by_lua* in ngx_stream_lua_module is planned although
there are some showstoppers to be resolved first :)
Best regards,
-agentzh
