Welcome! Log In Create A New Profile

Advanced

handle NGX_AGAIN properly

Julien Zefi
July 09, 2013 08:14PM
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 decide to finish sending out data (video frames).

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. But after that
happens, how can i restore my timer cycle ?

thnks.

J.Z.
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

handle NGX_AGAIN properly

Julien Zefi 1169 July 09, 2013 08:14PM

Re: handle NGX_AGAIN properly

Yichun Zhang (agentzh) 615 July 09, 2013 09:04PM

Re: handle NGX_AGAIN properly

Julien Zefi 660 July 13, 2013 08:22PM

Re: handle NGX_AGAIN properly

Yichun Zhang (agentzh) 564 July 14, 2013 02:42AM

Re: handle NGX_AGAIN properly Attachments

Julien Zefi 591 July 14, 2013 11:44PM

Re: handle NGX_AGAIN properly

wandenberg 639 January 03, 2015 07:00PM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 168
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready