Confirm
431
edits
Changes
→Implemention Questions
* The main problem with existing Listener classes is apparently (according to Boris) that some of them will have already read data from the HTTP body by the time OnStartRequest() is called. (What's the resulting problem here exactly? Has their OnDataAvailable() already been called on the main thread? Do they have some sort of state that would get messed up by the thread retarget?). Boris suggests that we can make some of these--most notably nsUnknownDecoder--safe by converting them from StreamListeners to nsIContentSniffers, so that they are no longer in the listener chain.
* If no Content-Type header was present in the HTTP reply, we sniff the content and possibly set up StreamConverters, etc. These might also need some work to be made thread-safe (the text/plain sniffer was mentioned in particular). ** Or--since missing Content-Type is quite rare for HTML content, which is all we're currently proposing to parse off-main-thread, we could simply refuse to redirect in this case?
* cache: no one seems to know exactly what mods might need to be made to the cache to support multiple simultaneous readers.
