Hi Julien,
I was having the same problem with NGX_AGAIN and could solved it.
Did you fix your problem?
I can try to help you.
Regards,
Wandenberg
On Thu, Jul 18, 2013 at 1:37 AM, Julien Zefi wrote:
> Hi all,
>
> thanks for the help but after more changes and taking in count your
> suggestions
Hi all,
thanks for the help but after more changes and taking in count your
suggestions i am still stuck with the problem (it cannot be in Lua, must be
done in C as i am streaming binary data).
If anyone of you is interested, i will put a budget of 100USD for who is
interested into fix the test c
Hello!
On Sun, Jul 14, 2013 at 8:43 PM, Julien Zefi wrote:
>
> Sorry by bother you again but i still cannot figure out how some internals
> are not working as i expect. I have take in count your suggestions and wrote
> a new test case (file attached).
>
1. You should simply call ngx_http_output_
Hi,
On Sun, Jul 14, 2013 at 12:40 AM, Yichun Zhang (agentzh)
wrote:
> Hello!
>
> On Sat, Jul 13, 2013 at 4:43 PM, Julien Zefi wrote:
> >
> > I have been trying many workarounds without luck, the last one that i
> have
> > is that if in my timer-callback the flush returns NGX_AGAIN, invoke a new
Hello!
On Sat, Jul 13, 2013 at 4:43 PM, Julien Zefi wrote:
>
> I have been trying many workarounds without luck, the last one that i have
> is that if in my timer-callback the flush returns NGX_AGAIN, invoke a new
> handler that sends out an empty chain, but it continue returning NGX_AGAIN,
> it n
Hi,
On Tue, Jul 9, 2013 at 7:02 PM, Yichun Zhang (agentzh) wrote:
> Hello!
>
> On Tue, Jul 9, 2013 at 5:12 PM, Julien Zefi wrote:
> > But if in some triggered callback by the timer the
> > ngx_http_output_filter(..) returns NGX_AGAIN *i assume* NginX will send
> that
> > chain as soon as the soc
Hello!
On Tue, Jul 9, 2013 at 5:12 PM, Julien Zefi wrote:
> But if in some triggered callback by the timer the
> ngx_http_output_filter(..) returns NGX_AGAIN *i assume* NginX will send that
> chain as soon as the socket becomes available again.
This assumption is not correct. Nginx will only flus
hi,
i understand that NGX_AGAIN is returned when a chain could not be send
because more data cannot be buffered on that socket.
I need to understand the following: in my case, when i receive a request, i
start a timer every 10ms and send out some data, then i create a new timer
every10ms until i
