On Jun 2, 2007, at 11:39, Anne van Kesteren wrote:
Sending mutation events is probably the only way to go.
Of course, real-world apps that want to use a streaming API probably want a drop-in SAX replacement and don't want to maintain a non- parser-exposed private DOM that could respond to the mutation events. (If they had a DOM-like tree internally, exposing it to the parser tree builder would probably be simpler than trying to hide it behind mutation events.)
In *practice*, streaming considerations mean SAX or rough equivalents (e.g. the expat native API).
-- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/
