• To: "'Dare Obasanjo'" <dareo@m...>,"'Elliotte Harold'" <elharo@m...>,<Neeraj.Bajaj@S...>
• Subject: RE: Article on JAXP 1.3 "Fast and Easy XML Processing"
• From: "Michael Kay" <mike@s...>
• Date: Thu, 17 Feb 2005 09:08:51 -0000
• Cc: "'Chris Burdess'" <dog@b...>,<xml-dev@l...>
• In-reply-to: <830178CE7378FC40BC6F1DDADCFDD1D1042DAC47@R...>
• Thread-index: AcUUYSZ8Z957zRd4QSK8TTM2ExrbAgAGSZaAAAGxlKAAE8dLIA==

> > 
> > Have you seen the alternatives, like the .NET transformation 
> > API with about 20 overloaded transform() methods?
> 
> So given the choice of methods that take useless interfaces 
> (since they
> have to cast to get anything useful) and APIs with lots of overloaded
> methods that support a rich set of data sources, why would 
> you think the
> former is better? 

(a) it's more extensible, and (b) it's more memorable for the user.

Michael Kay
http://www.saxonica.com/

• References:
  • RE: Article on JAXP 1.3 "Fast and Easy XML Processing"
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: Re: Why associate an attribute with a namespace ?
• Next by Date: RE: sequence with elements with the same name is not allowed?
• 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: Article on JAXP 1.3 "Fast and Easy XML Processing"
• Index(es):
  • Date
  • Thread