Confirm
431
edits
Changes
→A reasonable API target for now: sending OnDataAvailable() to other threads
At the April 2009 Platform work week we had a meeting on making necko support requests from threads other than the main thread. Here's some design notes on what we came up with.
== Is this even worth implementing given our plans for multiprocess? ==
So one very relevant question: do we even want to do this, given our move to using multiple processes (see [[Content_Processes]])?
The API described on this page allows very limited necko access to non-main threads in our current, single process architecture. The primary target is an off-main thread HTML parser. But if we're going to switch to a multi-process architecture, with the HTML parser in the subprocess(es), there seems to be little point in doing this work, too. They both achieve better UI/parser response times, and greater parallelism.
The only reason I can see for doing the API here is because we can implement it sooner. But since there's just one of me :), it would mean the subprocess implementation would be delayed.
== A reasonable API target for now: sending OnDataAvailable() to other threads ==
