- From: Nathan <nathan@webr3.org>
- Date: Fri, 10 Sep 2010 16:21:07 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: WebApps WG <public-webapps@w3.org>
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? Best, Nathan
Received on Friday, 10 September 2010 15:22:17 UTC