[Bug 235790] New: Review Request: perl-CGI-Prototype - Create a CGI application by subclassing

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.




https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235790

           Summary: Review Request: perl-CGI-Prototype - Create a CGI
                    application by subclassing
           Product: Fedora Extras
           Version: devel
          Platform: All
               URL: http://search.cpan.org/dist/CGI-Prototype/
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: normal
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: cweyl at alumni.drew.edu
         QAContact: fedora-package-review at redhat.com


SRPM URL: http://home.comcast.net/~ckweyl/perl-CGI-Prototype-0.9053-1.fc6.src.rpm
SPEC URL: http://home.comcast.net/~ckweyl/perl-CGI-Prototype.spec

Description:
The core of every CGI application seems to be roughly the same:

*   Analyze the incoming parameters, cookies, and URLs to determine the state
of the application (let's call this "dispatch").
* Based on the current state, analyze the incoming parameters to respond to
any form submitted ("respond").
*   From there, decide what response page should be generated, and produce it
("render").

CGI::Prototype creates a "Class::Prototyped" engine for doing all this, with
the right amount of callback hooks to customize the process.  Because I'm
biased toward Template Toolkit for rendering HTML, I've also integrated that
as my rendering engine of choice. And, being a fan of clean MVC designs, the
classes become the controllers, and the templates become the views, with clean
separation of responsibilities, and "CGI::Prototype" a sort of "archetypal"
controller.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.