Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams

[Martin Thomson <[e-mail]>]

On 25 April 2013 12:33, James M Snell <[e-mail]> wrote:
> Perhaps a simpler approach would be to just redefine the limit such
> that an endpoint MUST NOT have more than MAX_CONCURRENT_STREAMS in the
> Open state at any given time. We have already established that once
> the stream is half-closed, new frames cannot be sent, so once the
> server half-closes a steam it initiates, the counter is decremented
> and the server is permitted to initiate another stream. The client can
> choose to reject those additional streams if it chooses.

Do you mean that only outward bound streams count toward the
concurrency limit.  That could be workable; it's certainly easier to
explain.