• From: Miles Sabin <msabin@c...>
• To: David Megginson <david@m...>, XMLDev list <xml-dev@i...>
• Date: Tue, 18 Jan 2000 14:51:53 -0000

David Megginson wrote,
> We've talked in the past about supplying better DOM support in
> SAX2 through features and properties.  There are two options:
>
> 1. Pull

I don't think I like this much. Unless I've misunderstood
you're proposing that we hide a DOM-walking SAX event
generator behind a SAX property. I can't really see the
benefit of that. Why would you want to access such a thing
via this route rather than by simply creating one directly,
ie.,

  XMLReader reader = new DOMXMLReader(someDocument);

The earlier proposals I remember seemed more aimed at simply
allowing access to the current DOM node from a Document/Content
Handler. That seems reasonable, (tho' I'm having trouble 
thinking of any real applications).

> 2. Push
> [snip: DOMHandler]
> This saves a lot of unnecessary hashtable lookups.

Could you elaborate on that a bit?

Cheers,


Miles

-- 
Miles Sabin                       Cromwell Media
Internet Systems Architect        5/6 Glenthorne Mews
+44 (0)20 8817 4030               London, W6 0LJ, England
msabin@c...          http://www.cromwellmedia.com/


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ or CD-ROM/ISBN 981-02-3594-1
Please note: New list subscriptions now closed in preparation for transfer to OASIS.

• Follow-Ups:
  • RE: SAX2: DOM support
    • From: David Megginson <david@m...>

• Prev by Date: Re: Alternatives to browsers (was Re: Alternatives to the W3C)
• Next by Date: RE: SAX2: DOM support
• Previous by thread: SAX2: DOM support
• Next by thread: RE: SAX2: DOM support
• Index(es):
  • Date
  • Thread