ISSUE-113: How do we represent HTTP POST?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

ISSUE-113: How do we represent HTTP POST?

SWD Issue Tracker


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.

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?



Reply | Threaded
Open this post in threaded view
|

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

Maciej Stachowiak


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


Reply | Threaded
Open this post in threaded view
|

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

Charles McCathieNevile-2

On Thu, 08 Mar 2007 11:48:09 +1100, Maciej Stachowiak <[hidden email]> 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
[hidden email]          Try Opera 9.1     http://opera.com