[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What should TrAX look like? (Was: Re: Article on

• To: Elliotte Harold <elharo@m...>
• Subject: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• From: Chris Burdess <dog@b...>
• Date: Sun, 20 Feb 2005 09:02:37 +0000
• Cc: XML Developers List <xml-dev@l...>
• In-reply-to: <42176B5A.2010608@m...>
• References: <E1D2Si4-0001QA-00@u...> <42176B5A.2010608@m...>

Elliotte Harold wrote:
> It occurred to me that it might be possible to design this as some 
> sort of iterator interface like DOM's NodeIterator. Streaming 
> implementations  would only be able to walk this in a forward fashion.

I can see this working for pull parsers, but it's not clear to me how 
it might integrate with a callback-style API.

>  Then there could be a tree-based subclass of this interface that 
> added methods for moving backwards, and along the independent axes.

This is exactly what I proposed:

>> an object resembling a tree navigator that can be used to iterate 
>> over the nodes in the tree and retrieve individidual node objects 
>> (more complex but object model agnostic, should perhaps be combined 
>> with a property (a URI?) indicating the object model(s) supported).

As well as navigating around the tree (previous, next, first-child, 
parent) it could be used to retrieve properties of the current node 
(name, type, value), using a node adapter specific to the object model.
-- 
Chris Burdess

• References:
  • RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: "Michael Kay" <mike@s...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>

• Prev by Date: Re: Substitution Groups
• Next by Date: Re: Transmitting XML between different applications
• Previous by thread: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Next by thread: RE: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread