Re: What error code when concurrent stream limit is exceeded

That is a separate problem. We are only talking about the violation of
settings here.

You are right that this is a general problem, but not a new one. This is
partly why we encourage large concurrency limits, and only use SHOULD when
talking about the single connection.


On Mon, Nov 24, 2014, 01:46 Michael Sweet <msweet@apple.com> wrote:

What about proxies? They can advertise a limit but the upstream server may
have different limits. Short of opening extra connections to support the
required amount of concurrency, seems like it should be able to tell the
client it has reached a limit and to try again later...