Nginx Module (I/O block)
alexander_koch_log at lavabit.com
Tue Mar 5 23:01:44 UTC 2013
On 02/10/2013 12:25 AM, Maxim Dounin wrote:
> On Sat, Feb 09, 2013 at 04:41:54PM +0100, alexander_koch_log wrote:
>> It is not clear to me how to avoid blocking the nginx reactor loop
>> when creating an nginx module which should perform some long I/O
>> operations and return the response to the client. Or is this
>> handled internally by Nginx?
> Correct aproach is to avoid blocking for a long time, and use
> non-blocking I/O and event-based notification instead.
> What exactly should (and can) be done depends on the exact case.
> E.g. to work with sockets there are lots of various functions
> available to simplify things. Working with files without blocking
> is harder and not always possible, but a common case is handled by
> nginx - to send some large file you just have to open the file and
> ask nginx to send an in-file buffer.
When sending an in-file buffer, is it still possible to have the read
stop when a special byte char is read like \xFF even though the provided
bytes to read are larger?
One way would be to read to the buffer then truncate the memory, then
send the buffer? Or is there an efficient way?
More information about the nginx-devel