Ports Search

In MyApp.pm: use Catalyst qw/LogWarnings/; After that, any warn statement that's executed during action processing is sent to the log $c->log as a warning (instead of being dumped to STDERR).

Many dynamic websites perform heavy processing on most pages, yet this information may rarely change from request to request. Using the PageCache plugin, you can cache the full output of different pages so they are served to your visitors as fast as possible. This method of caching is very useful for withstanding a Slashdotting, for example. This plugin requires that you also load a Cache plugin. Please see the Known Issues when choosing a cache backend.

Ruby on Rails has a nice feature to create nested parameters that help with the organization of data in a form - parameters can be an arbitrarily deep nested structure. The way this structure is denoted is that when you construct a form the field names have a special syntax which is parsed. This plugin supports two syntaxes: dot notation <input name="foo.bar.gorch" /> subscript notation <input name="foo[bar][gorch]" /> When reading query parameters from $c->req you can now access all the items starting with "foo" as one entity using $c->req->param('foo');. Each subitem, denoted by either the dot or the square brackets, will be returned as a further deeper hashref.

Catalyst::Plugin::Pluggable is a plugin for pluggable Catalyst applications.

A Catalyst plugin for Prototype.

Run code after the response has been sent.

This plugin allows you to schedule events to run at recurring intervals. Events will run during the first request which meets or exceeds the specified time. Depending on the level of traffic to the application, events may or may not run at exactly the correct time, but it should be enough to satisfy many basic scheduling needs.

FastMmap sessions for Catalyst.

This plugin allows you to write e.g. shopping cart code which should behave well for guests as well as permanent users. The basic idea is both logged in and not logged in users can get the same benefits from sessions where it doesn't matter, but that logged in users can keep their sessions accross logins, and will even get the data they added/changed assimilated to their permanent account if they made the changes as guests and then logged in. This is probably most useful for e-commerce sites, where the shopping cart is typically used before login, and should be equally accessible to both guests and logged in users.

The Session plugin is the base of two related parts of functionality required for session management in web applications. The first part, the State, is getting the browser to repeat back a session key, so that the web application can identify the client and logically string several requests together into a session. The second part, the Store, deals with the actual storage of information about the client. This data is stored so that the it may be revived for every request made by the same client. This plugin links the two pieces together.