• From: Uche Ogbuji <uche.ogbuji@f...>
• To: lyndavv@e...
• Date: Thu, 22 Feb 2001 07:18:55 -0700 (MST)

> My customers have continued using protocols like MQ instead of XML with XSLT
> for EAI in integration between components and automated workflow because of
> performance issues.  When talking with David Turner (Microsoft), he calls
> them "perceived performance issues."  Is performance of XSLT implementations
> for largescale EAI/B2B integrations real or perceived?

Well, how old is MQ Series?  How old is XSLT?  How old is XQuery?

MQ is efficient because it has developed its efficiency.  XSLT
implementations will have to do a lot of maturing before they catch up,
but so will XQuery implementations.

No one is saying that people move to Saxon, MSXSL or 4XSL for large-scale
document query.  My point is that XSLT has a sufficient framework that
with some lightweight additions, very efficient implementations can and
will emerge.


-- 
Uche Ogbuji                               Principal Consultant
uche.ogbuji@f...               +1 303 583 9900 x 101
Fourthought, Inc.                         http://Fourthought.com
4735 East Walnut St, Ste. C, Boulder, CO 80301-2537, USA
Software-engineering, knowledge-management, XML, CORBA, Linux, Python

• Follow-Ups:
  • RE: XSLT Performance (was BLANK)
    • From: johns@s... (John F. Schlesinger)

• Prev by Date: Re: XQuery -- Reinventing the Wheel?
• Next by Date: RE: XQuery -- Reinventing the Wheel?
• Previous by thread: Re: XSLT Performance (was BLANK)
• Next by thread: RE: XSLT Performance (was BLANK)
• Index(es):
  • Date
  • Thread