Re: Unidirectional streams PR

[Christian Huitema <[e-mail]>]

On 6/29/2017 9:57 AM, Mike Bishop wrote:
>
> Moot point – there is no concurrent stream limit in the protocol. 
> There is only a maximum stream ID, and how your implementation decides
> what maximum stream ID to issue to the peer allows you to choose any
> resolution to these questions you like.
>
OK, my bad.

> Now, in the unidirectional or mixed designs, you do have the corner
> case where a client can send a request, but not give the server enough
> Stream IDs to respond.  (Don’t do that.)  More realistically, the
> server can have a limited number of Stream IDs and spend them on
> pushes instead of actual responses
>

I am looking at the "mixed" scenario, in which the client would open an
unidirectional stream with an associated "stream N" in the other
direction. Will we say that doing so automatically pushes the server's
maximum stream ID to some value greater than N?

-- 
Christian Huitema