W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: BLOCKED frame specification

From: Yoav Nir <ynir.ietf@gmail.com>
Date: Wed, 9 Apr 2014 12:17:02 +0300
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <151D22D3-8BA2-41F1-BD47-7D863F780DCE@gmail.com>
To: David Krauss <potswa@gmail.com>

On Apr 9, 2014, at 12:02 PM, David Krauss <potswa@gmail.com> wrote:

> On 2014Ė04Ė09, at 4:59 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:
>> That only tells me if the connection is working, not if the resources are not coming because of some server issue (like trouble connecting to a back-end database) or because of flow control.
> Use the implementation-defined payload value. Itís not portable but you donít need portability for debugging.

Looking at section 6.7 of -11 I donít see any implementation-defined payload value, just some opaque data that the receiver should copy into its response. 

Even if there was, I would be debugging my implementation against some other implementation. Not against my own.

Received on Wednesday, 9 April 2014 09:17:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:29 UTC