Hello,

On 2/4/16 3:15 AM, SplitIce wrote:
> The map module is also a noticeable omission tied into the lack
> of variables.
>
> On Thu, Feb 4, 2016 at 11:13 AM, Yichun Zhang (agentzh)
> <agentzh@gmail.com <mailto:agentzh@gmail.com>> wrote:
>
> Hello!
>
> On Wed, Feb 3, 2016 at 3:37 PM, SplitIce wrote:
>> I have been taking a look at the Stream modules for use in a
>> particular application. I noticed the entire subsystem lacks
>> any variable support.
>>
>> Is variable support planned? Is there a significant reason for
>> the omission?
>>
>
> +1
>
> I'm also looking forward to NGINX variable support in the
> "stream" subsystem.
>
> I'm currently emulating some of the builtin NGINX variables of
> the "http" subsystem in my ngx_stream_lua_module on the Lua
> land, like $pid, $connection, $remote_addr, $server_addr, and
> etc:
>
>
> https://github.com/openresty/stream-lua-nginx-module#nginx-api-for-lua
>
>
> Actually I'm also looking for "send_timeout", "send_lowat",
> "resolver", "resolver_timeout", "lingering_close",
> "lingering_time", "lingering_timeout", "postpone_output" and etc
> directives in the stream {} context so that each of my stream
> typed NGINX modules do not have to re-invent these over and over
> again.
>
Thanks for the input. This is something we have in the stream
roadmap but no ETA so far.

As the stream module is rather new and almost unknown for the most of
nginx users we really want to collect more feedback from users about
basic and missed features in the stream modules.

--
Maxim Konovalov

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel