Re: Stream state and PUSH_PROMISE

Hi Martin:

I am interested in the case where an open stream receives a PUSH_PROMISE on that stream with another stream id to be used. The RFC, as best I read it, does not specify that it goes into a half-open local/remote or any other state for the promised stream. 

Thanks,

Hadil G. Sabbagh, Ph. D.


> On Jul 10, 2017, at 5:14 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> On 11 July 2017 at 09:37, Hadil Sabbagh <hadil.sabbagh@xeia.io> wrote:
>> What is the state of the stream when a PUSH_PROMISE is sent or received when the stream is in the OPEN state?
> 
> Which stream is open, the stream on which the PUSH_PROMISE is sent, or
> the one that is promised?
> 
> The latter case is interesting because that means that you are
> sending/receiving two PUSH_PROMISE frames that promise the same stream
> (and the first one has been acted upon already).  That's an error,
> according to the following text from Section 5.1:
> 
>> In the absence of more specific guidance elsewhere in this document, implementations SHOULD treat the receipt of a frame that is not expressly permitted in the description of a state as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

Received on Tuesday, 11 July 2017 00:56:47 UTC