Re: Can AxKit be used as a Template Engine?

[Ian Kallen <[EMAIL PROTECTED]>]

Mason and AxKit solve different but related problems.  The former a
code-aware component system with process semantics that lend itself to
easily scoping a component's applicability, the latter a transformation
engine.  It would be nice to see a framework published that uses the best
of both (sorry, I don't have time to do it myself :).  The Java world
suffers from the same disconnect, in fact I think it's worse there; JSP
and Cocoon don't play together (I've never seen a servlet chainging
example that shows them doing so).

On Mon, 23 Apr 2001, Matt Sergeant wrote:
> Having said that, it goes the other way too - currently building web
> applications is probably a lot easier with Mason than it is with AxKit,
> because that's what it was designed for. AxKit has a pretty cool
> technology called XSP, which gives you a cold-fusion like system of
> inserting tags into your XML for dynamic functionality. But in my opinion
> it doesn't scale well (in the development sense, not in the performance
> sense) to large applications, because it is inherently a page-based
> technology (like PHP, Cold Fusion, JSP, ASP, etc), and I don't think
> page-based web development systems scale well to larger applications. I
> prefer something that is turned inside-out from the page based view of
> things, like MVC.

cheers,
-Ian

--
Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen