W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: [google-gears-eng] Re: Deploying new expectation-extensions

From: Charles Fry <fry@google.com>
Date: Wed, 17 Sep 2008 07:36:05 -0400
Message-ID: <b549193f0809170436taeb5667i8d7a783da2c1e074@mail.gmail.com>
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Cc: "Mark Nottingham" <mnot@mnot.net>, "Mark Nottingham" <mnot@yahoo-inc.com>, "Julian Reschke" <julian.reschke@gmx.de>, gears-eng@googlegroups.com, "Alex Rousskov" <rousskov@measurement-factory.com>, "HTTP Working Group" <ietf-http-wg@w3.org>

> I wonder if a new 100-class code, the inverse of CONTINUE, wouldn't be of
> value in HTTP/next to designate that a the request body can be omitted since
> a final determination is available.  The client would still have to send a
> body (since there is no ack) but using a chunked send, a chunk of 0 bytes
> to finalize an empty request body would be sufficient.

But if there will be any new 1xx response code, then it should be the
103 (Checkpoint) from our proposal. Because if you can use that then
you can just include the entire body in the first post, using the 103
to obtain whatever information you need to resume upon failure (e.g.
etag or new location).

Charles
Received on Wednesday, 17 September 2008 11:36:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:54 GMT