• To: Michael Kay <mike@s...>, 'Pete Cordell' <petexmldev@t...>, xml-dev@l...
• Subject: XSLT processor internals (was RE: Another XML parsing idea?)
• From: Mukul Gandhi <mukul_gandhi@y...>
• Date: Thu, 14 Jul 2005 15:11:45 -0700 (PDT)
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=GiNtWx9QhIeqlIpNVJz0VsvM48FFDjzpemQrEmGZCkd5eBSVetiaXq2W99dUon8WjfhJu9QdfjbAz/EJqSp+6xCGPZUVVhbeikzm6aMeQ1PE5H32QrHquvRqUFh6iF4XPj3ELQUFWcj5Dw8d4BvPW2o8GtK0y/MWWCCrq1lfICA= ;

Thanks Mike for your thoughts.. Your views are precise
and accurate. Now I give up this topic. 

I start an unrelated topic. How do you implement
xsl:template name="something" and its required
instruction xsl:call-template in the XSLT processor.
i.e. what kind of data structures do you use in Java
and what kind of control flow takes place. Am just
curious since many days..

Regards,
Mukul

--- Michael Kay <mike@s...> wrote:

> It's entirely possible, but it's also unnecessary,
> since there are perfectly
> good Java parsers around. If you have to run
> applications on a heterogeneous
> platform, then you want to put the boundary where
> the amount of chat is
> lowest.
> 
> Michael Kay
> http://www.saxonica.com/
> 
> 
> 



		
__________________________________ 
Yahoo! Mail for Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail 

• Follow-Ups:
  • RE: XSLT processor internals (was RE: Another XML parsing idea?)
    • From: "Michael Kay" <mike@s...>

• Prev by Date: RE: Another XML parsing idea? Was: Re: XML Hangover)
• Next by Date: RE: XSLT processor internals (was RE: Another XML parsing idea?)
• Previous by thread: Re: Simple XSLT Problem
• Next by thread: RE: XSLT processor internals (was RE: Another XML parsing idea?)
• Index(es):
  • Date
  • Thread