Well it looks like we need to implement x, but need to decide on if/how that is exposed to extensions. Right now all the event handlers get an event object: https://searchfox.org/mozilla-central/source/dom/webidl/StreamFilterDataEvent.webidl Is there any data that could be added for these to indicate anything about thee part that is being processed? Is it possible that different parts may be processed at the same time? e.g. onstart (part 1) onstart (part 2) ondata (part 1) ondata (part 2) onstop (part 1) ondata (part 2) onstop (part 2) If so, I think it's important to have some extra data on the event object. If it all happens synchronously, then we could just document that. During onAfterLastPart we could issue an additional onstop with some flag that the request is complete, or we could add something like a StreamFilter.onMultiPartComplete event. Matt, do you have any thoughts or input on the above?
Bug 1638422 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Well it looks like we need to implement nsIMultiPartChannelListener, but need to decide on if/how that is exposed to extensions. Right now all the event handlers get an event object: https://searchfox.org/mozilla-central/source/dom/webidl/StreamFilterDataEvent.webidl Is there any data that could be added for these to indicate anything about thee part that is being processed? Is it possible that different parts may be processed at the same time? e.g. onstart (part 1) onstart (part 2) ondata (part 1) ondata (part 2) onstop (part 1) ondata (part 2) onstop (part 2) If so, I think it's important to have some extra data on the event object. If it all happens synchronously, then we could just document that. During onAfterLastPart we could issue an additional onstop with some flag that the request is complete, or we could add something like a StreamFilter.onMultiPartComplete event. Matt, do you have any thoughts or input on the above?