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

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 04 Apr 2008 16:01:58 +0200
Message-ID: <47F634D6.3040808@gmx.de>
To: Brian McBarron <bpm@google.com>
CC: google-gears-eng@googlegroups.com, Charles Fry <fry@google.com>, Mark Nottingham <mnot@yahoo-inc.com>, HTTP Working Group <ietf-http-wg@w3.org>

Brian McBarron wrote:
> ...
> What we need to implement 
> http://code.google.com/p/google-gears/wiki/ResumableHttpRequestsProposal 
> is a mechanism which:
> A) Is guaranteed to reach the origin-server (not discarded or refused by 
> a proxy)
> B) The origin-server will refuse to process if it doesn't understand
> These conditions are necessary so that the continuation of a request 
> can't result in unintended consequences if it ends up at the wrong 
> origin-server.  Charles and I thought that the Expect header would 
> accomplish these two things.  Does anyone have a suggestion for a 
> different mechanism that could achieve the same effect?
> ...

It sounds you need a Must-Understand end-to-end mechanism. I don't think 
that exists in HTTP/1.1. RFC 2774 may be what you want, but that doesn't 
help in practice.

That being said, I'm not sure why you need B).

Can't the origin server just send the 103s without being asked for it? 
That would allow the client to discover support for the feature.

BR, Julian
Received on Friday, 4 April 2008 14:02:44 GMT

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