2012/6/5 l.jay Yuan <pass86@gmail.com>:
> okay, 3Q.
> another question, in ngx_wsasend.c 's ngx_wsasend function
>
> #if 0 // is test code?or really should do it?
>       if ((size_t) n < size) {
>           wev->ready = 0;
>       }
> #endif
>

As of the current release 'ready' flag is reset there. You should
update nginx sources.

ngx_handle_write_event() belongs to upper layer interface and is
anyways expected to be called.

> 2012/6/5 Vladimir Shebordaev <vshebordaev@mail.ru>:
>> 2012/6/5 l.jay Yuan <pass86@gmail.com>:
>>> sorry, fix: call ngx_handle_write_event?
>>>
>>> 2012/6/5 l.jay Yuan <pass86@gmail.com>:
>>>> if i do not call ngx_handle_write_event  the ngx_connection_t 's
>>>> ngx_event_t *write will never be handler.
>>>> it means after c->send(c, buf, n) then call c->send(c, buf, n)?
>>>>
>>
>> Yes, you should firstly process the data then update the connection
>> state for the next event, i.e. call ngx_handle_write_event()
>>
>>>> 2012/6/5 Vladimir Shebordaev <vshebordaev@mail.ru>:
>>>>> Hi!
>>>>>
>>>>> ngx_handle_write_event() is the event processiong state machine
>>>>> interface function that is to proper update event and connection
>>>>> states after write event is fired and the data has been probably
>>>>> written to the corresponding descriptor. It can optionally update
>>>>> send_lowat option on the connection socket.
>>>>>
>>>>> --
>>>>> Regards,
>>>>> Vladimir
>>>>>
>>>>>
>>>>> 2012/6/5 l.jay Yuan <pass86@gmail.com>:
>>>>>> when to call ngx_handle_write_event?i am not really understanded.
>>>>>> who can explain me?
>>>>>>
>>
>> _______________________________________________
>> nginx-devel mailing list
>> nginx-devel@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>

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