Re: [quicwg/base-drafts] Identify streams unidirectional vs bidirectional based on stream ID (#872)

[Ryan Hamilton <[e-mail]>]

On Tue, Oct 17, 2017 at 4:33 PM, Martin Thomson <[e-mail]>
wrote:

> So that I don't forget this... This PR omits two very important things:
>
>    1.
>
>    It doesn't actually say what a unidirectional stream *is*.
>
> ​Doh.​
​ I'm not awesome at spec language. I tried to define this implicitly by
saying that "

​"​
Unidirectional streams created by the peer are
​ ​
immediately half-closed (local) to the receiver and are subsequently treated
​ ​
identically to a half-closed bidirectional stream.
​"​
​

But that's probably not terribly useful. Have a suggestion on test?

>
>    1.
>    2.
>
>    It doesn't say anything about stream usage in HTTP.
>
> As we discussed on the editor's call today, we are going to merge this,
> then fix it. I'll prioritize fixing the first issue though.
>

​Are you planning to merge this as is, or shall I address some of the other
feedback (the table, for example).​

> Given the HTTP usage, I'm going to push harder for a separation of the
> type bits, because that will make the HTTP usage of the identifiers easier
> (it has implicit type identification). That will have to wait until #877
> <https://github.com/quicwg/base-drafts/pull/877> resolves. That also
> needs some HTTP text.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/pull/872#issuecomment-337409206>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ASp6yt7lvT26YAtK3F1nj3Fql4Tu3SDAks5stTldgaJpZM4P4257>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/872#issuecomment-337746754