Regex dispatch types have been depreciated and removed from Catalyst core. It is
recommend that you use Chained methods or other techniques instead. As part of
the refactoring, the dispatch priority of Regex vs Regexp vs LocalRegex vs
LocalRegexp may have changed. Priority is now influenced by when the dispatch
type is first seen in your application.
CGI::FastTemplate manages templates and parses templates replacing variable
names with values. It was designed for mid to large scale web applications (CGI,
mod_perl) where there are great benefits to separating the logic of an
application from the specific implementation details.
Catalyst::Engine::Apache - Catalyst Apache Engines
These classes provide mod_perl support for Catalyst.
This engine is designed to run as a standalone Catalyst server, without
requiring the use of another web server. It's goals are
high-performance, HTTP/1.1 compliance, and robustness. It is also
suitable for use as a faster development server with support for
automatic restarting.
PSGI engine for Catalyst.
An _extremely_ lightweight CGI processing package provides _minimum_
functions needed such as form decoding (including file upload forms),
URL encoding and decoding, HTTP usable date generation (RFC1123 compliant
dates) and basic escaping and unescaping of HTMLized text.
Enable your CGI.pm aware applications to adapt PSGI protocol.
Catalyst::Enzyme is a layer on top of the Catalyst framework providing
CRUD functionality for Class::DBI models.
Enzyme uses convention and configuration to provide e.g. extensible
CRUD out-of-the-box, and a common way of dealing with error handling
etc.
It's not completely unlike Maypole in this regard. However, at this
point Enzyme isn't as feature-rich as Maypole.
Enzyme is one way of bringing many Catalyst modules and concepts
together into a unified whole. There are other ways to do this
(obviously. This is, like... uh, Perl).
CGI::Response is a Perl5 module for constructing responses to
Common Gateway Interface (CGI) requests. It is designed to be
light-weight and efficient for the most common tasks, and also
to provide access to all HTTP response features for more
advanced CGI applications.
There are two ways to use CGI::Response.
For basic applications, the Simple Interface provides a number
of plain functions that cover the most commonly-used CGI
response headers.
More advanced applications may employ the Full Interface object
methods to access any HTTP header, or to add experimental or
non-standard headers. Both interfaces try to generate reasonable
defaults whenever possible.
Catalyst::Helper::Controller::Scaffold is a helper for scaffolding for
Catalyst, which adds easy scaffolding:
# Imagine you want to generate a scaffolding controller MyApp::C::SomeTable
# for a CDBI table class MyApp::M::CDBI::SomeTable
script/myapp_create.pl controller SomeTable Scaffold CDBI::SomeTable