Re: log_by_lua!

Thanks again for your time and consideration. I was already trying to implement body "downstream" reading, and just location.capture only to stora...

agentzh · 2012-05-04T10:50:38+00:00

Thanks again for your time and consideration. I was already trying to implement body "downstream" reading, and just location.capture only to stora...

Re: log_by_lua!

agentzh

On Fri, May 4, 2012 at 2:37 AM, Matthieu Tourne
<matthie...@gmail.com> wrote:
> Check out : https://github.com/mtourne/lua-nginx-module
>
> I wrote the documentation, markdown and a useful example this time.
>
> I'll also document the other feature I added to ngx.req.init_body,
> append_body, finish_body.
>
> Again it'll be great if you start integrating. Or at least review the
> changes.
>

That's awesome! I'll surely look at your patches!

But I'm currently busy with my wedding ceremony and I'll start
reviewing and integrating your patches after 10 May. During the
meantime I can only answer trivial mails or submit trivial patches :P

Thank you for your patience! And sorry again for the delay on my side!

Best regards,
-agentzh

P.S. I'm cc'ing the openresty mailing group:
https://groups.google.com/group/openresty/ So that other developers
can see this! :D

wd

I think it's something like a mmap? Not logs like the access_log or error_log.

On Fri, May 4, 2012 at 10:50 AM, agentzh <age...@gmail.com> wrote:
> On Fri, May 4, 2012 at 2:37 AM, Matthieu Tourne
> <matthie...@gmail.com> wrote:
>> Check out : https://github.com/mtourne/lua-nginx-module
>>
>> I wrote the documentation, markdown and a useful example this time.
>>
>> I'll also document the other feature I added to ngx.req.init_body,
>> append_body, finish_body.
>>
>> Again it'll be great if you start integrating. Or at least review the
>> changes.
>>
>
> That's awesome! I'll surely look at your patches!
>
> But I'm currently busy with my wedding ceremony and I'll start
> reviewing and integrating your patches after 10 May. During the
> meantime I can only answer trivial mails or submit trivial patches :P
>
> Thank you for your patience! And sorry again for the delay on my side!
>
> Best regards,
> -agentzh
>
> P.S. I'm cc'ing the openresty mailing group:
> https://groups.google.com/group/openresty/ So that other developers
> can see this! :D
>
>

agentzh

On Fri, May 4, 2012 at 11:16 AM, wd <...@wdicc.com> wrote:
> I think it's something like a mmap? Not logs like the access_log or error_log.
>

AFAIK, the log_by_lua* thing is a just "log-phase" handler. It does
not necessarily generate logs nor access shared memory storage. It
runs the same phase as the standard ngx_log module that usually
generates access logs.

Matthieu's patch effectively solves the following github issue:

    https://github.com/chaoslawful/lua-nginx-module/issues/51

Best regards,
-agentzh

matthieu.tourne

On Thu, May 3, 2012 at 8:42 PM, agentzh <age...@gmail.com> wrote:

On Fri, May 4, 2012 at 11:16 AM, wd <...@wdicc.com> wrote:
> I think it's something like a mmap? Not logs like the access_log or error_log.
>

AFAIK, the log_by_lua* thing is a just "log-phase" handler. It does
not necessarily generate logs nor access shared memory storage. It
runs the same phase as the standard ngx_log module that usually
generates access logs.

This is correct, it doesn't generate logs per se.

There is an example in the doc on how to aggregate simple values and output them using a content handler in another location.

Don't hesitate to email me directly if you have questions, openresty users!

Matthieu's patch effectively solves the following github issue:

https://github.com/chaoslawful/lua-nginx-module/issues/51

Best regards,
-agentzh

wd

I see, thanks for the explain.

On Fri, May 4, 2012 at 11:46 AM, Matthieu Tourne
<matthie...@gmail.com> wrote:
>
>
> On Thu, May 3, 2012 at 8:42 PM, agentzh <age...@gmail.com> wrote:
>>
>> On Fri, May 4, 2012 at 11:16 AM, wd <...@wdicc.com> wrote:
>> > I think it's something like a mmap? Not logs like the access_log or
>> > error_log.
>> >
>>
>> AFAIK, the log_by_lua* thing is a just "log-phase" handler. It does
>> not necessarily generate logs nor access shared memory storage. It
>> runs the same phase as the standard ngx_log module that usually
>> generates access logs.
>>
>
> This is correct, it doesn't generate logs per se.
>
> There is an example in the doc on how to aggregate simple values and output
> them using a content handler in another location.
>
> Don't hesitate to email me directly if you have questions, openresty users!
>
>>
>> Matthieu's patch effectively solves the following github issue:
>>
>>    https://github.com/chaoslawful/lua-nginx-module/issues/51
>>
>> Best regards,
>> -agentzh
>
>
>