[Libwebsockets] lws_rx_flow_control problem

Andy Green andy at warmcat.com
Tue Oct 10 04:03:56 CEST 2017

On October 10, 2017 7:56:40 AM GMT+08:00, Per Bothner <per at bothner.com> wrote:
>On 10/09/2017 04:40 PM, Andy Green wrote:
>> Managing flow control on a wsi from outside a callback on the wsi
>isn't really supported atm... whether it's a child or not doesn't make
>any difference.
>> In the http2 megapatch rx flow control accepts flags now and you can
>individually toggle up to 8 reasons for flow control on the wsi, if any
>reason is active it is suppressed.  It's completely
>backwards-compatible with just giving it 0 or 1 as before.  How about a
>flag you can give in the arg indicating that lws needs to do the
>_lws_rx_flow_control() in the call for that one?
>That sounds like it would work.

It's pushed on master in the h2 patch.  I added docs on lws_rx_flow_control(), basically OR LWS_RXFLOW_REASON_FLAG_PROCESS_NOW on the enable arg.


More information about the Libwebsockets mailing list