Re: h2 proxy and connection flow control

On Thu, Aug 21, 2014 at 11:12 PM, Patrick McManus <mcmanus@ducksong.com>
wrote:

>
>
>
> On Thu, Aug 21, 2014 at 10:09 AM, Tatsuhiro Tsujikawa <
> tatsuhiro.t@gmail.com> wrote:
>
>>
>>
>>
>> ​In this scenario, proxy has no room to expand. Therefore I wrote that​
>> all streams on backend connections are stalled.
>>
>>
> This is my point. If the proxy really has no room to expand (its out of
> ram) - then we've got a resource problem not a protocol problem. If it does
> have more ram, then just use the protocol to open the window to match the
> resources available.
>
>
​So if there is no ram to spend for that connection, is stalling entire
connection inevitable consequence (and we should not care about it)? ​
Connection flow control is limit the memory commitment for proxy then why
do we need to extend it in the response to a client behavior?

Best regards,
Tatsuhiro Tsujikawa