On Fri, 5 Apr 2002, Jason Foster wrote:
[... other frameworks ...]
> Cocoon
> - you code your *logic* in a procedural language and the runtime handles
> "continuations"
> - you code your *presentation* as individual web pages created using
> transformations and/or embedded scripting
> - the logic can make use of the presentation, which in turn can continue
> the logic
Wow, this sounds deep. Reminds me of when I coded in Prolog (a declarative
logic programming language), I never knew which object could in which
circumstances call which other object - and just as I thought I understood
the flow, the Runtime was up to something on its own :)
I have spent the last couple of days thinking about the following problem.
Suppose in an XSP page you have this flow control code:
if (test==true) {
<foo>bar</foo>
}
else {
<bar>foo</bar>
}
Rewrite this procedural code in a declarative way. After much fiddling
about I came to the conclusion that there is no elegant and practical
solution. But perhaps you guys can solve this problem on a higher level,
one advantage of Cocoon is that there are plenty of higher levels :)
cheers,
Ulrich
--
Ulrich Mayring
DENIC eG, Softwareentwicklung
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
