Make the current Catalyst request context available in Models and
Views.
Models and Views don't usually have access to the request object,
since they probably don't really need it. Sometimes, however, having
the request context available outside of Controllers makes your
application cleaner. If that's the case, just use this module as a
base class.
Return a new instance a component on each request
Catalyst::Controller::ActionRole is a perl module that apply roles to
action instances.
Coro based PSGI web server.
This plugin lets you put your lexicals on the stash and elsewhere very easily.
If you use the same name for two variables with the same storage binding
attribute they will be aliased to each other, so you can use this for reading
as well as writing values across controller subs. This is almost like sharing
your lexical scope.
This creates a new HTML::FormFu object, passing as it's argument
the contents of the "constructor" config value.
Protect your site from robots
This module decodes a URL-encoded parameter string in the manner of
CGI.pm. However, as it uses C code from libapreq to perform the task,
it's somewhere from slightly to much faster (depending on your strings)
than using CGI or a functionally similar module like CGI::Deurl.
This controller automatically generates and validates unique tokens across
multiple HTTP requests (form submits). You can use it to prevent duplicate
submits, or to protect against CSRF attacks.
The "Catalyst::Devel" package includes a variety of modules useful for
the development of Catalyst applications, but not required to run them.
This is intended to make it easier to deploy Catalyst apps. The runtime
parts of Catalyst are now known as "Catalyst::Runtime".
"Catalyst::Devel" includes the Catalyst::Helper system, which autogenerates
scripts and tests; Module::Install::Catalyst, a Module::Install extension
for Catalyst; and requirements for a variety of development-related modules.
The documentation remains with Catalyst::Runtime.