From: "Tom Allison" <[EMAIL PROTECTED]>
Todd W wrote:
From: "Tom Allison" <[EMAIL PROTECTED]>
Second: The website speaks of an Apache::Template for mod_perl but
implies it's still 'expiremental'. Considering that slashcode is
written with this (I think) is this still true?
Apache::Template works well and I'd bet many people have it in
production (I do), but be aware that it still leaves you much work to do
in terms of building your web app framework (Sessions, Auth, Model OO
Wrappers, Login/Logout, etc) as processing templates is only a part of
building out your app.
My favorite frameworks are CGI::Application and Catalyst. If you are
curious as to why those frameworks, search CPAN for Catalyst::Plugin or
CGI::Application::Plugin and read the descriptions of the modules. After
figuring out how to leverage the plugins, the time between design and
business logic implementation of a typical web app averages out to a few
weeks or even a few days.
Doesn't Catalyst become kind of huge with all the dependencies?
Catalyst definitely isn't petite, but in practice it functions fine as a
high performance web app server. Plus the features it offers are so enticing
that its not a problem for me to build out the app and then go back in and
refactor where needed.
CGI::Application, on the other hand, is very minimal. As an example, here is
a link I wrote up to a self contained CGI::Application app that shows how to
utilize the session plugin:
http://cgiapp.erlbaum.net/cgi-bin/cgi-app/index.cgi?CgiApplicationPluginSessionExample
Todd W.
_______________________________________________
templates mailing list
[email protected]
http://lists.template-toolkit.org/mailman/listinfo/templates
