On Mon, 23 Apr 2001, Ian Kallen <[EMAIL PROTECTED]> wrote:
> 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).
Actually what I'm looking at and talking to Phillipe about right now is
somehow doing the thing Smartworker does, but using XML and
transformations, and adding in AxKit's abilities to detect the requesting
device and "do the right thing". I think that would be the best way to
build large scale web apps for multiple delivery targets.
The alternative of course it to just plug them both together - AxKit and
Mason play nicely together using Apache::Filter (though it's a bit slow).
--
<Matt/>
/|| ** Founder and CTO ** ** http://axkit.com/ **
//|| ** AxKit.com Ltd ** ** XML Application Serving **
// || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
// \\| // ** mod_perl news and resources: http://take23.org **
\\//
//\\
// \\
