Re: DOM tree update

Although I'm just getting started with all of these W3C "standards", it
seems like a good architecture
would be to treat the programs initialization separate from the
re-reading of the dynamic changes to
the file.  Multiple files should probably be used to eliminate the
chance of missed changes or events.
With XSL (or more precisely XSLT), a second file could represent the
changes to original
file.  Without more detail of your requirements, one possible
architecture is:

    Initialization: file.xml is created
    Process A -> writes to modification.xslt
    Process B (initialization) -> reads file.xml, combines changes with
modification.xslt, creates internal
            DOM data structure and writes file.xml.  Also clears
modification.xslt to the point of where it read.
            This file would be a FIFO queue, obviously implementation
specific.
    Process A -> writes to modification.xslt
    Process B -> applies modification.xslt to internal DOM data
structure (when the file has been modified by Process
            A), clears modification.xslt to the point it used.

    Notes:
        XSLT, as I understand it, can make virtually any modifications
to an XML file.

    Options:
        -When file.xml is updated
        -Choice of FIFO
        -use MVC pattern


>      I am using XML and the DOM to organize data : the XML file
>      is parsed, and a
>      DOM tree is generated.
>      The problem is that the data varies in real time ; is it
>      possible to update
>      the DOM tree without re-parsing the whole xml file ?(which
>      would be too
>      time-consuming). I want the DOM tree to reflect the changes,
>      without re-parsing everything.
>      Is it possible, and where could I find information about how
>      to do this ?
>
>      Thanks a lot for your help,
>
>      Regards,
>
>      Benedicte
>      LIP6, Paris, France
>      desclefs@rp.lip6.fr
>      http://www.lip6.fr/~rp/~desclefs/wwwwwwwwwwwwwww
>

Received on Thursday, 8 July 1999 12:39:32 UTC