So a script cannot execute concurrently with the traversal of the DOM tree? Could this be a performance bottleneck?
Fady On Mon, Jan 4, 2010 at 9:41 PM, James Robinson <jam...@google.com> wrote: > On Mon, Jan 4, 2010 at 6:36 PM, Peter Kasting <pkast...@google.com> wrote: > >> On Mon, Jan 4, 2010 at 6:32 PM, Fady Samuel <fadysam...@gmail.com> wrote: >> >>> I know I'm asking you a lot of questions here. >>> >> >> And you keep removing chromium-dev. Why? I'm not the knowledgeable >> person about much of this stuff, I'm just trying to be helpful. >> >> Alex mentioned the Webkit DOM tree, indicating that making the nodes of >>> the DOM tree immutable in this fashion would be interesting. >>> >> >> Why? AFAIK the DOM tree isn't shared across processes, and the renderer >> is effectively single-threaded as far as this is concerned. >> >> How does the current traversal of the DOM tree work? Does it require >>> locking? Do you create a copy of the tree for rendering purposes? >>> >>> I assume scripting enables dynamic updates of the DOM tree to happen all >>> the time? I haven't looked into this much myself yet. How is the >>> synchronization handled there currently? >>> >> > All access to the DOM and related data structures happens from the same > thread. This is deeply embedded into the design. > > - James > > > >> >> As I said, I believe the DOM tree isn't shared across processes, so there >> is no synchronization that I know of. >> >> I am way out of my depth in this area so you really should not ask me >> specifically. >> >> PK >> >> -- >> Chromium Developers mailing list: chromium-dev@googlegroups.com >> View archives, change email options, or unsubscribe: >> http://groups.google.com/group/chromium-dev >> > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
