ISSUE-107: End state events in multi-object transactions

multi-object end events

End state events in multi-object transactions

State:

CLOSED

Product:

HISTORICAL: Progress Events [features subsumed by XHR; worked stopped]

Raised by:

Charles McCathie Nevile

Opened on:

2009-10-19

Description:

Where a transaction has multiple objects (i.e. there is a loadedItems attribute present, and a value other than 1 for totalItems), should the end events (load/abort/error be fired for each object, or only on the completion of the entire transaction?

I am assuming loadend should only fire at the end of the complete transaction (that might be a dumb assumption) but my current thinking is that it makes sense to fire a final event for each transaction (for example to learn what happened to each object, potentially allowing a request for only those that didn't come through cleanly the first time.

For now this is left open in the editor's draft.

Related Actions Items:

No related actions

Related emails:

1. Re: Proposal for sending multiple files via XMLHttpRequest.send() (from chaals@opera.com on 2009-10-20)
2. Re: Use cases (appcache, etc) [progress] (from chaals@opera.com on 2009-10-20)
3. Re: Use cases (appcache, etc) [progress] (from annevk@opera.com on 2009-10-20)
4. Re: Use cases (appcache, etc) [progress] (from chaals@opera.com on 2009-10-20)
5. New Progress events draft: 1.32 (from chaals@opera.com on 2009-10-20)
6. ISSUE-107 (multi-object end events): End state events in multi-object transactions [Progress Events] (from sysbot+tracker@w3.org on 2009-10-19)

Related notes:

Display change log