CGI::Prototype is remarkably flexible, scaleable and practical. That
being the case, this is more of a philsophical question than any.
However, it is a fact that for most websites, the content-type will be
text/html for most of the pages and that the actual content will vary
on each page.
This being the case, should these two aspects of the CGI response be
two different methods, with $self->content_type existing in a base
class and re-used for most of the app and $self->content (which is
known as $self->render) be variant on each page?
--
Carter's Compass: I know I'm on the right track when,
by deleting something, I'm adding functionality.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
cgi-prototype-users mailing list
cgi-prototype-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cgi-prototype-users
