xml-axkit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sergeant <m...@sergeant.org>
Subject Re: cvs commit: xml-axkit/lib/Apache/AxKit/Language XSP.pm
Date Tue, 05 Mar 2002 13:24:17 GMT
On Tue, 5 Mar 2002, Jörg Walter wrote:

> On Tuesday, 05. March 2002 12:41, you wrote:
>
> > Yes, that's what I was thinking too. I'm just not sure right now if SAX is
> > a good way to go for XSP, since I honestly think it would be slower for
> > us.
>
> Depends on how you use it. I guess most people are just fine with a DOM-based
> implementation, because they are generating one web page's worth of XML. The
> DOM is already there, so XSLT will start up faster. Perhaps some day people
> will start using XSP for large database retrieval?
> But then again, virtually every AxKit-generated content goes through XSLT or
> XPS, which would at least defy the memory saving effect (correct me if I'm
> wrong). So I would agree to your doubts, web-centric XML processing won't get
> that large soon.

Eventually we'll have Barrie write a XML::Filter::Dispatch based XSLT
look-alike using streaming XPaths. Until that day it's probably not worth
worrying about (lets do one step at a time, is all I'm suggesting).

> We should place that 'no attr after child elements'
> restriction anyways.

100% agreed.

-- 
<!-- Matt -->
<:->Get a smart net</:->


Mime
View raw message