On Fri, 13 Jun 2008 15:01:35 +0200, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
On Fri, 13 Jun 2008 13:43:09 +0200, Charles McCathieNevile
<[EMAIL PROTECTED]> wrote:
On Wed, 28 May 2008 13:01:13 +0200, Anne van Kesteren
<[EMAIL PROTECTED]> wrote:
Yesterday someone contacted me on IRC about implementing
XMLHttpRequest.upload from XMLHttpRequest Level 2. It turns out that
the Progress Events specification is not generic enough for both
uploading and downloading as we agreed it should be long ago.
The ProgressEvent.loaded member should probably be defined in a more
abstract way
Can you explain in more detail what should be changed? (Feel free to
raise a new issue for this in the webapps tracker - otherwise I will
when I understasnd a bit more clearly what the issue is about).
Well, it says "Specifies the number of bytes downloaded since the
beginning of the download." for ProgressEvent.loaded for instance while
that same member should cover the "upload" cases (data transfer from
client to a server instead of the other way around).
Yep, makes sense. Will play with the text...
...
Overall, but I think this issue was already raised, it's not really
clear which bits are filled in by the specification using Progress
Events and which bits are filled in by the Progress Events specification.
Do you have any concrete suggestions for changes, e.g. to the section on
usng Progress Events in specifications in the current editor's draft [1],
or the Public draft, or can you explain what is unclear? Failing that, can
you explain what you did understand so far?
cheers
Chaals
--
Charles McCathieNevile Opera Software, Standards Group
je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals Try Opera 9.5: http://snapshot.opera.com
