W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: Progress Events normative text

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 18 Jun 2009 10:28:48 -0700
Message-ID: <63df84f0906181028y45e1dc01i30b763b23f83e04d@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Charles McCathieNevile <chaals@opera.com>, Ian Hickson <ian@hixie.ch>, public-webapps@w3.org
On Wed, Jun 17, 2009 at 5:49 AM, Anne van Kesteren<annevk@opera.com> wrote:
> On Mon, 15 Jun 2009 17:00:46 +0200, Charles McCathieNevile <chaals@opera.com> wrote:
>> On Sat, 13 Jun 2009 13:54:10 +0200, Anne van Kesteren <annevk@opera.com>
>> wrote:
>>> That definitely makes sense, though please take into consideration that
>>> for cross-origin loads exposing the file size cannot be done until all
>>> HTTP headers have been received and the requested resource has opted in
>>> with CORS.
>>
>> OK. One of the things I intended to keep leaving to the "host" spec was
>> definining what the size actually refers to.
>
> I'd think we would like this to consistently refer to the entity body for all usage of progress events as to not
> confuse people using the API. It seems odd to take great care in order and naming but not in consistent
> implementation of the event objects.

At the very least we can define that for HTTP request, headers are not
used. For things like WebSocket and FutureAwesomeMegaAlienProtocol it
might make sense to do something different, perhaps.

/ Jonas
Received on Thursday, 18 June 2009 17:29:44 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT