-------- Original Message --------
From: Frank Wiles <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: modperl@perl.apache.org
Subject: Re:Filtering and Separation of Presentation Layer
Date: Mon Dec 26 2005 16:26:21
On Mon, 26 Dec 2005 14:17:00 +0100
Joachim Zobel <[EMAIL PROTECTED]> wrote:
I think it makes sense to use Apache filtering to seperate the
presentation layer. The idea is to have an application layer that
outputs xml and a template engine attached by filtering that merges
the xml into html pages.
What is already there? Are there any template engines that can be
attached through filtering? Is there any spec. for an interface xml?
What are the cons of this approach?
Separating your application like that is a great idea, most large
applications do this type of separation inside of the app itself.
While I haven't heard of anyone doing this in practice, I have at
times thought about it.
I have been wondering recently about separation of presentation and data
in the context of AJAX - whilst keeping the presentation still
server-side. Anyone doing anything interesting in this space with mod_perl?
Our current approach is as Frank describes - two layers within the
server application (data generation and presentation), rather than the
filter idea floated by Joachim.
I think a server presentation later/filter, has to be preferred to
complex client-side Javascript rendering engines? Javascript is a PITA
to code and debug, and there are too many buggy versions out there.
Thoughts?
Regards,
Jeff
