W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: XHR2 proposal: support for informational responses

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 10 Sep 2010 17:36:50 +0200
Message-ID: <4C8A5092.9070008@gmx.de>
To: nathan@webr3.org
CC: WebApps WG <public-webapps@w3.org>
On 10.09.2010 17:21, Nathan wrote:
> Julian Reschke wrote:
>> Hi,
>> it might be cool (and not too complicated) to (optionally) expose 1xx
>> responses to the caller (see
>> <http://greenbytes.de/tech/webdav/rfc2616.html#status.1xx>).
>> This could be done through an opt-in, such as specifying a callback
>> function to be called asynchronously when the messages come in
>> (returning status line and headers).
>> I know, I know: few use cases. But that's of course because HTTP
>> stacks currently do not provide support for it.
>> See <http://tools.ietf.org/html/draft-decroy-http-progress-04> for an
>> older proposal, which, as far as I recall, got experimental support in
>> Chromium.
> Sounds like a good idea, + is this not needed to allow servers to tell
> clients to Upgrade to HTTP+TLS or WebSockets?

I was thinking of status codes other than 101, such as 102 defined in 
RFC 2518, and being discussed again it the draft mentioned above (this 
would be for progress notifications).

Best regards, Julian
Received on Friday, 10 September 2010 15:37:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:11 UTC