IMHO, the only
clean way of fully separating content/business logic and presentation is by having your Perl-scripts provide XML-data (this is the content/business logic part) and then transforming this XML into HTML (this is thr presentation part) by using XSLT and CSS. This can be done server-side (think of
Axkit) or client-side (e.g. IE 6). I find it much better than a templating system, which always feels either a bit restricted or too complicated, but never entirely right.
And of course XMS, XSLT, ... are hip buzzwords and mucho liked by PHB.
CountZero
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
|
Re^2: Multi tiered web applications in Perl
by adrianh (Chancellor) on Oct 21, 2003 at 21:58 UTC
|
IMHO, the only clean way of fully separating content/business logic and presentation is by having your Perl-scripts provide XML-data
Much as I love XML in some circumstances this is just nonsense :-)
XML is no better (or worse) than any other transport mechanism. You can misuse XML just the same way you can misuse any other transport mechanism.
| [reply] |
|
|
Well mankind has a great talent to misuse anything.
CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
| [reply] |
