Re: PR 70: Adding uni-directional stream support to QUIC

As I pointed out on the PR, I'm in favor of it.

The breakup of a bidirectional stream into methods/attributes for a read
direction and a write direction for use in unidirectional streams feels
natural and seems to fit well.

The simplification of the states down to just readable/writable also seems
like a good improvement.



On Sat, Oct 6, 2018 at 12:35 PM Bernard Aboba <Bernard.Aboba@microsoft.com>
wrote:

> Seth Hampson has been working on adding uni-directional stream support to
> the WebRTC-QUIC API. The PR is here:
>
> https://github.com/w3c/webrtc-quic/pull/70
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-quic%2Fpull%2F70&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C6b1c76f871d14d5bfbea08d62bc27090%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636744511447053227&sdata=lY%2BSMhEPQJdV3W9LAsMgmn6h%2BZZevoZpYwQGXC%2FciyY%3D&reserved=0>
>
> The spec with changes applied is here:
>
>
> https://rawgit.com/w3c/webrtc-quic/unidirectional-streams-and-state-update/index.html
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwebrtc-quic%2Funidirectional-streams-and-state-update%2Findex.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C6b1c76f871d14d5bfbea08d62bc27090%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636744511447053227&sdata=UQN7E1%2BgLxwBGqOb9RoPhvrZjTVHLeUBZ96zEiwB37o%3D&reserved=0>
>
> Since this is a *major* revision affecting multiple interfaces, methods
> and attributes, we are soliciting feedback.
>
>