On Tue, 19 Nov 2002, Coexec wrote: > Date: Tue, 19 Nov 2002 15:40:37 -0800 (PST) > From: Coexec <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Migrating from CGI.pm to Apache::Request question. > > Hello all, I have been searching through the mailing > list archives for the answer to my question, but I > have not found it. > > I am experienced with using the CGI.pm, and now I want > to rewrite all of my CGI's using mod_perl and > Apache::Request. According to everything that I have > been reading, the Apache::Request module handles only > GET, POST and Cookie data, and no HTML. Basically, my > question is, what is the most commonly used module for > generating HTML like the CGI.pm does ? > > Thanks
There are so many different ways to handle HTML generation that it will make your head spin. You're always welcome to continue using CGI.pm's methods for generating HTML, but that usually couples the logic and presentation of your application so tightly that it makes for less-than-maintainable code -- less than what, however, remains the question. Many people like to use templating systems (HTML::Template, Template::Toolkit), some like to use more all-inclusive packages (Mason, Apache::ASP, Embperl), some people just use "print" statements (arguably the worst choice). Asking what is the most common way people on this list won't likely generate a consensus; ask 10 people how they do this and you'll probably get 10 different answers. As for me, I'm quite partial to Template::Toolkit. You'll have to decide what works best for you. No need to use a sledgehammer to drive a finishing nail. Use whatever tool is the simplest to use for your situation, but no simpler. :-) ky
