Changes for version 5.80030 - 2011-01-04
- New features:
- Add a --proc_title option to the FCGI script to set the process title.
- Allow the response body to be set to `undef' explicitly to indicate the absence of a body. It can be used to indicate that no body should be sent at all and processing of views should be skipped. This is especially useful for things like X-Sendfile, which now no longer require providing fake response bodies to suppress view processing. In order for this to work, you will also have upgrade Catalyst::Action::RenderView to at least version 0.15.
- Bug fixes:
- Deal correctly with GLOB file handles in the response body (setting the Content-Length header appropriately)
- Chained dispatch has been fixed to always prefer paths with the minimum number of captures (rather than the maximum number of actions). This means that (for example) a URI path /foo/* made out of 2 actions will take preference to a URI path /*/* made out of 3 actions. Please check your applications if you are using chained action and please write new test to report failing case.
- Stop relying on bugs in the pure-perl version of Package::Stash. New versions of Package::Stash load Package::Stash::XS if available. Package::Stash::XS fixes some of the bugs of the pure-perl version, exposing our faulty assumption and breaking things. We now work with both old and new versions of Package::Stash, both with and without Package::Stash::XS being installed. Older versions of Catalyst-Runtime also work with both old and new versions of Package::Stash, but only if Package::Stash::XS is *not* installed.
- Documentation:
- Clarify that when forwarding or detaching, the end action associated with the original dispatched action will be run afterwards (fallen)
Documentation
Overview of changes between versions of Catalyst
Instructions for upgrading to the latest Catalyst
Bootstrap a Catalyst application
Modules
The Elegant MVC Web Application Framework
Catalyst Action
Chain of Catalyst Actions
Catalyst Action Container
Deprecated base class
Class data accessors
Catalyst Component Base Class
Moose Role for components which capture the application context.
Moose Role for components which need to close over the $ctx, without leaking
Catalyst Controller base class
DispatchType Base Class
Path Part DispatchType
Default DispatchType
Index DispatchType
Path DispatchType
Regex DispatchType
The Catalyst Dispatcher
The Catalyst Engine
The CGI Engine
FastCGI Engine
Catalyst HTTP Engine
Catalyst Exception Class
Basic Catalyst Exception Role
Exception for redispatching using $ctx->detach()
Exception for redispatching using $ctx->go()
Role defining the interface for Catalyst exceptions
Catalyst Log Class
Catalyst Model base class
provides information about the current client request
handles file upload requests
stores output responding to the current client request
The Catalyst Framework Runtime
The CGI Catalyst Script
Create a new Catalyst Component
The FastCGI Catalyst Script
Catalyst test server
Test Catalyst application on the command line
Common functionality for Catalyst scripts.
The Catalyst Framework script runner
Catalyst Timing Statistics Class
Test Catalyst Applications
The Catalyst Utils
Catalyst View base class
Provides
in lib/Catalyst/Exception.pm