Re: [quicwg/base-drafts] Make RST_STREAM a bit on STREAM frame (#775)

[ekr <[e-mail]>]

On Mon, Sep 18, 2017 at 3:19 PM, Ryan Hamilton <[e-mail]>
wrote:

> When you receive a STREAM frame, don't you have to look up the stream in
> order to deliver the stream data? In other words, I'm surprised that it's
> any less work to handle receipt of a RST_STREAM frame than it is to handle
> receipt of a STREAM frame with a build-in RST_STREAM semantic. Would you
> like to have only one place in the code which does the stream id to stream
> lookup? (That place being receipt of a STREAM frame).
>

Yes. And I'd like to have it dispatch essentially anything of that type to
the stream.


> Keep in mind that depending on how you implement things, receipt of a
> WINDOW_UPDATE frame needs to frob the stream as does receipt of an ACK
> frame for a packet containing data sent by that stream.
>

Well, WINDOW_UPDATE is now MAX_DATA and MAX_STREAM_DATA, so it's ready to
be made a stream frame.


-- 
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/issues/775#issuecomment-330422776