W3C home > Mailing lists > Public > public-webapi@w3.org > March 2007

Re: ISSUE-113: How do we represent HTTP POST?

From: Charles McCathieNevile <chaals@opera.com>
Date: Thu, 08 Mar 2007 19:11:01 +1100
To: "Maciej Stachowiak" <mjs@apple.com>, "Web APIs WG" <public-webapi@w3.org>
Message-ID: <op.tou2cnlgwxe0ny@widsith.local>

On Thu, 08 Mar 2007 11:48:09 +1100, Maciej Stachowiak <mjs@apple.com> wrote:

> On Mar 7, 2007, at 4:40 PM, Web APIs Issue Tracker wrote:

>> POST can upload a pile of stuff, and then download a body. So there
>> are
>> two parts of the transaction whose progress would be useful to track.
>> Further, these are in principle synchronous, and you don't know
>> anything at all about the second part until you have finished the
>> first
>> one.
>
> The upload part would be represented via events on xhr.upload, if we
> go with the recent proposal. The download would be events on the
> XMLHttpRequest object itself.
>
>> Are there other problems of this nature? Is the best solution to make
>> this the problem of XHR and similar specs that allow this
>> situation, or
>> to provide something in the progress spec?
>
> I think we decided to leave this to other specs to solve - any object
> that does both upload and download should provide separate event
> targets.

Works for me. I will try to clarify in the next draft of the specification that other specifications should describe where and when to fire these events. I suppose it is also possible to write a spec for something that has multiple operations firing progress - say, downloading a page and all its linked resources. If someone wanted to do that.

cheers

Chaals

-- 
  Charles McCathieNevile, Opera Software: Standards Group
  hablo español  -  je parle français  -  jeg lærer norsk
chaals@opera.com          Try Opera 9.1     http://opera.com
Received on Thursday, 8 March 2007 08:11:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT