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

Re: What should TrAX look like? (Was: Re: Articleon

• To: Wolfgang Hoschek <whoschek@l...>
• Subject: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• From: Elliotte Harold <elharo@m...>
• Date: Wed, 23 Feb 2005 08:07:48 -0500
• Cc: kjouk@y..., xml-dev@l...
• In-reply-to: <e3e82eebdc6fa9346729066b1497431b@l...>
• References: <E1D2Si4-0001QA-00@u...> <200502211623.51418.kjones@s...> <421A0ECF.3090802@m...> <200502220742.53890.kjouk@y...> <421B03D2.6020803@m...> <e3e82eebdc6fa9346729066b1497431b@l...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041217

Wolfgang Hoschek wrote:

> This has less to do with the structure of an iternal model, and more to 
> do with more or less clever optimization/indexing independent of the 
> object model.

Then such a tool could build an index over the LCD tree without 
reconstructing the tree.

> I remember running a very simple "//item" with the XOM CVS XPath toy. 
> Turns out it would have taken a month to run to completion - quadratic 
> time complexity where one would expect O(N). With another engine it ran 
> in less than a second. Similar for other queries.

If you have an actual test case that demonstrates the issue, I suspect I 
can fix it. However, allegations on mailing lists without any actual 
data rarely result in improvements.

-- 
Elliotte Rusty Harold  elharo@m...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

• Follow-Ups:
  • Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Wolfgang Hoschek <whoschek@l...>

• 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: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Kevin Jones <kjones@s...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>
  • Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Wolfgang Hoschek <whoschek@l...>

• Prev by Date: Re: Why you should avoid Notation Declarations (by Kohsuke
• Next by Date: Re: Why you should avoid Notation Declarations (byKohsuke
• Previous by thread: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by thread: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread