[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: xml-dev@l...
• Subject: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• From: Kevin Jones <kjones@s...>
• Date: Mon, 21 Feb 2005 16:23:51 +0000
• Cc: Elliotte Harold <elharo@m...>
• In-reply-to: <42178F8D.8070904@m...>
• Organization: Sarvega Inc
• References: <E1D2Si4-0001QA-00@u...> <200502191742.28139.kjones@s...> <42178F8D.8070904@m...>
• Reply-to: kjones@s...
• User-agent: KMail/1.6.2

On Saturday 19 February 2005 19:12, Elliotte Harold wrote:
> What they would get from an LCD interface is a way to
> write the code that converts into their internal
> representations that is independent of the specific model
> used. Currently, something like BEA's XQuery engine has
> to accept XOM, SAX, DOM, etc. They have to write a custom
> converter for each of these. If there were an LCD
> interface that were rich enough to populate their
> internal data model, but no richer, then they would only
> have to write that conversion logic once. Furthermore,
> they could easily support object models they didn't even
> know about, as long as those models provided an adapter
> to the LCD interface.

We clearly have very different objectives here. I think 
maybe at the core is that a LCD model is always going to 
compromise performance. I am tied of working with models 
that do this because they make my job harder. 

I can see why something simpler is appealing but think they 
are often short sighted in a way. When one of the 
limitations becomes a problem, off we go and create yet 
another model with just slightly different properties.

I was hoping there might be a way out of that circle. Maybe 
I should go off and think about how I would tackle this a 
bit more coherently. Thanks for enlightening me about why 
things go this way.

Kev.

• Follow-Ups:
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>

• 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...>

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