Lists Home |
Date Index |
- To: "Paul R Brown" <email@example.com>,"XML Developers List" <firstname.lastname@example.org>
- Subject: RE: [xml-dev] What should TrAX look like? (Was: Re: [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
- From: "Dare Obasanjo" <email@example.com>
- Date: Thu, 17 Feb 2005 12:11:45 -0800
- Cc: "Elliotte Harold" <firstname.lastname@example.org>,"Michael Kay" <email@example.com>
- Thread-index: AcUVJTRU0QGCpXvnQ06GM0kXvCUgFQAB5Spg
- Thread-topic: [xml-dev] What should TrAX look like? (Was: Re: [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
> -----Original Message-----
> From: Paul R Brown [mailto:firstname.lastname@example.org]
> Sent: Thursday, February 17, 2005 11:14 AM
> To: 'XML Developers List'
> Cc: 'Elliotte Harold'; Michael Kay
> Subject: Re: [xml-dev] What should TrAX look like? (Was: Re:
> [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
> I also go so far as to say that the discussion is a bit misdirected:
> the apparently poor encapsulation of Source is more of a
> symptom of the fact that TrAX transformers (e.g., XSLT
> processors but potentially STX or XQuery or...?) need to be
> able to implement their underlying model however they so
> choose. Source is little more than a marker interface, and
> the thing that makes sense (at least to me) is to have
> off-the-beaten-path Source implementations (e.g., for a pull
> parser) exhibit enough polymorphism (implement SAXSource,
> DOMSource, etc.) to make them useful and reasonably portable
> for consumption by different Transformer implementations.
Marker interface is a synonym for design flaw.
PITHY WORDS OF WISDOM
No matter how long or how hard you shop for an item, after you've bought
it, it will be on sale somewhere cheaper.
This posting is provided "AS IS" with no warranties, and confers no