[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

• Subject: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• From: Bill de hÓra <bill.dehora@p...>
• Date: Thu, 17 Feb 2005 13:20:41 +0000
• Cc: 'XML Developers List' <xml-dev@l...>
• In-reply-to: <E1D1lMG-0002Gf-00@u...>
• References: <E1D1lMG-0002Gf-00@u...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

>>I think we've all implicitly agreed that Source is pretty 
>>useless. 

I don't seem to be getting all the mail in this thread, but to whomever 
said that, please count me out of your consensus.


> The 
>>primary argument in its favor has been a lot of hand waving 
>>and pointing 
>>at some .NET thing, and saying, "That's even worse" but 
>>nobody's really 
>>stepped up to defend Source on its own merits.

Well, I said that the .NET approach is missing an abstraction. I'm 
willing to speculate that when that abstraction is found it will look 
like a Source object, but with a means of reading off metadata that the 
polymorphic approach is calling out explicitly.

Mike is right - Source is a better basis for this kind of API, it's just 
not fully baked in Saxon today.


>Michael Kay wrote:
> Only, I think, by forcing the "arbitrary model" to implement some kind of
> standard interface like SAX or DOM - and that would defeat the whole
> purpose, even if it were an improved SAX or an improved DOM.

I think you could also work off a dictionary approach. Personally I'd 
rather start evolving from a cast than 20 overloaded methods. Every time 
I see a cast I see a query for more information.

cheers
Bill

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

• Prev by Date: RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• Next by Date: RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• 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: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread