Confirmed users
431
edits
Necko: support sending OnDataAvailable() to other threads: Difference between revisions
Necko: support sending OnDataAvailable() to other threads (view source)
Revision as of 20:34, 6 May 2009
, 6 May 2009→Implemention Questions
| Line 39: | Line 39: | ||
* If no Content-Type header was present in the HTTP reply, we sniff the content and possibly set up StreamConverters, etc. (the text/plain sniffer was mentioned in particular). We may need to teach StreamConverters to switch threads. | * If no Content-Type header was present in the HTTP reply, we sniff the content and possibly set up StreamConverters, etc. (the text/plain sniffer was mentioned in particular). We may need to teach StreamConverters to switch threads. | ||
** 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? | ** 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? | ||
* TransactionPumps and the HttpProtocolHandler will probably need work to work with thread redirection. | |||
* We may want to move some logic that currently runs in the main thread into the necko thread: gzip converstion came up in particular. | |||
* cache: no one seems to know exactly what mods might need to be made to the cache to support multiple simultaneous readers. | * cache: no one seems to know exactly what mods might need to be made to the cache to support multiple simultaneous readers. | ||
| Line 48: | Line 51: | ||
* A large number of classes would need modification: nsURI, nsChannels, IIOService and the various nsIProtocolHandlers. | * A large number of classes would need modification: nsURI, nsChannels, IIOService and the various nsIProtocolHandlers. | ||
* Authorization boxes would need to be popped up from non-main threads | * Authorization boxes would need to be popped up from non-main threads | ||
* Many of the necko APIs have been implemented by Javascript extensions, which would suddenly need to be thread-safe | * Many of the necko APIs have been implemented by Javascript extensions, which would suddenly need to be thread-safe. | ||