Re: [libmicrohttpd] Regarding Flow control

[Santos Das]

Hi Christian,

Thank you. Could you please explain how the TCP's flow control mechanism is helping in this case. A few lines would be great, please.

thanks, santos

On Tue, Sep 18, 2018 at 3:18 PM Christian Grothoff <address@hidden> wrote:

Hi!

Good news: You don't need to do anything.  MHD will maintain persistent
TCP connections and use TCP's flow control mechanisms automatically.
You can _force_ MHD to not keep connections open by adding "Connection:
Close" to your HTTP response header manually, but by default MHD will do
the right thing.

This is independent of your threading model or the use of suspend/resume.

Happy hacking!

Christian

On 09/17/2018 05:33 PM, Santos Das wrote:
> Hi,
>
> Just to add more, my application is single threaded and I am running MHD
> inside that. I don't create additional threads. I use suspend and resume
> as suggested earlier as I do async processing.
>
> So, I am thinking how can we implement flow control in this scenario..
>
> Thanks, Santos
>
>
>
> On Mon, Sep 17, 2018 at 8:22 PM Santos Das <address@hidden
> <mailto:address@hidden>> wrote:
>
>     Hi,
>
>     Could you kindly let me know how can we implement the flow control ?
>     Protection against the badly behaving clients.
>
>
>     HTTP/1.1 servers SHOULD maintain persistent connections and use TCP's flow control
>
>     mechanisms to resolve temporary overloads, rather than terminating connections with
>
>     the expectation that clients will retry. The latter technique can exacerbate network
>
>     congestion.
>
>      
>
>     https://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
>
>
>     Thanks, Santos
>
>