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

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

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 7 Mar 2007 16:48:09 -0800
Message-Id: <DDC6E542-A60D-4F11-82BB-A617369A8124@apple.com>
To: Web APIs WG <public-webapi@w3.org>


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

>
>
> ISSUE-113: How do we represent HTTP POST?
>
> http://www.w3.org/2005/06/tracker/webapi/issues/113
>
> Raised by: Charles Mccathienevile
> On product: Progress Event
>
> 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.

Regards,
Maciej
Received on Thursday, 8 March 2007 00:48:17 GMT

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