Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits

This does differ from SPDY, but (still) seems reasonable given the number
of streams created in the initial RTT shouldn't be unbounded anyway.
Assuming we have persisted settings (which is in doubt, I guess), this
would only be a problem for the first RTT in a session where we didn't have
the persisted setting.


On Fri, May 3, 2013 at 11:04 AM, James M Snell <jasnell@gmail.com> wrote:

> Currently in the trunk:
>
>     indicates the maximum number of concurrent streams that the sender
> will allow.
>     This limit is directional: it applies to the number
>     of streams that the sender permits the receiver to create. By
> default there is no
>     limit.  It is recommended that this value be no smaller than 100,
>     so as to not unnecessarily limit parallelism.
>
>
>
> On Fri, May 3, 2013 at 10:52 AM, William Chan (陈智昌)
> <willchan@chromium.org> wrote:
> > The setting is there, but I don't see the initial limit, which I believe
> was
> > 100.
> >
> >
> > On Fri, May 3, 2013 at 2:47 PM, James M Snell <jasnell@gmail.com> wrote:
> >>
> >> Which limits specifically? SETTINGS_MAX_CONCURRENT_STREAMS is still
> >> there. Are there others you're concerned about?
> >>
> >> On Fri, May 3, 2013 at 10:37 AM, William Chan (陈智昌)
> >> <willchan@chromium.org> wrote:
> >> > Did the stream limits disappear by accident?
> >
> >
>
>