No doubt it will be a significant effort but it would hopefully demonstrate the effectiveness of my copy-on-write, and read-copy-update techniques to enable efficient strongly consistent iterators in a real-world application, and so I can ultimately graduate. :P
Of course, my thesis advisor thinks no one cares about this stuff so I have to prove him wrong. Fady 2010/1/5 Jens Alfke <[email protected]> > > On Jan 4, 2010, at 7:50 PM, Fady Samuel wrote: > > > I'm not disagreeing with you. Yes, the script needs to see a coherent > state as it executes BUT the renderer only needs a logically consistent > snapshot, correct? So the script can work on the most current version of the > DOM, while the renderer does its thing to produce a bitmap from the > snapshot? > > This could potentially be done, but if you're running V8 and the renderer > on different threads, both of them still need to be able to call directly > into the DOM and many other parts of WebCore, none of which have been > designed to be multi-threadable. The "snapshot" of the DOM would, I suspect, > end up being a copy of most of the renderer's data structures, which would > significantly increase memory use. (Yes, you could limit this by using > copy-on-write techniques, but you'd have to apply those techniques to > zillions of mutation points all over WebCore.) > > —Jens
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
