Seperating content and presentation on websites - any views on Apache::PageKit?

snapdragon has asked for the wisdom of the Perl Monks concerning the following question:

Morning all,

I'm about to start work at a new place and they mentioned in the interview that they use Apache::Pagekit for a lot of their applications. As far as I can see Apache::PageKit is a web applications framework that is based on mod_perl - it seems to be aimed at trying to seperate out static and dynamic content on websites (so that designers and developers don't mess with each others code).

I've used other such systems in the past (like Apache::ASP - my what a fresh hell that experience that was) with differing success. So has anyone out there used Apache::Pagekit? Can they recommend it / condemn it? Has anyone else seen any decent Open Source alternatives (I've had a play with various closed systems - like Vignette for example - and I think the cost prohibits them for most sites I'd be working on)?

Thanks in advance.......

Comment on Seperating content and presentation on websites - any views on Apache::PageKit?

Replies are listed 'Best First'.
Re: Seperating content and presentation on websites - any views on Apache::PageKit? by derby (Abbot) on Mar 15, 2002 at 13:36 UTC
snapdragon, check out the appservers, section of http://perl.apache.org for an overview of perl appservers. Also check out Joshua Chamas' benchmarking of those (and others). -derby	[reply]
Re: Seperating content and presentation on websites - any views on Apache::PageKit? by perrin (Chancellor) on Mar 15, 2002 at 16:49 UTC
Apache::PageKit is a good system. It takes HTML::Template and adds a structure for building applications and integration of Apache::Session. However, these days I'm more likely to recommend OpenInteract. It uses Template Toolkit, and I think it has a more useful translation of the model-view-controller pattern for web applications. It also has more pre-built components which can be handy if you're doing something that requires a user/group model and permissions. You can read more about the other options in my article. I have to say, I think that Apache::ASP is a really good option for people who like to use an in-line perl, page-centric coding style. Personally, I prefer to use more of a MVC, mini-language style.	[reply]