Changes

In a perfect world, our goal would This API allows non-main threads be an API where any thread could use allowed to directly receive the OnDataAvailable() call from the full necko nsIStreamListener interface, and initiate and process network requests completely independently. However, while there's no theoretical reason why necko couldn't be made fully re-entrant, All setup of the implementation obstacles involved network channel before this point (and possibly after) would need to be considerable handled on the main thread (see notes at end i.e. the non-main thread would not call any necko functions itself: it would instead arrange for some detailsthe main thread to call them).

Benjamin Smedberg suggested a much more modest goal: that non-main threads be allowed to directly receive the The OnDataAvailable() call from the nsIStreamListener interface. All setup of the network channel before this point (and possibly after) would need to be handled on the main thread. The meeting quickly came delivery appears to a consensus that something like this would be sufficient for the existing use cases for which a multithreaded necko has been requested: most notably, for an off-main-thread HTML parser to be able to stream in HTML from the network without interfering/delaying the main thread (and vice versa).