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
