Ports 搜索

This is the DBIx::Class model class for Catalyst. Whilst it allows you to use DBIC as your model in Catalyst, it does not make your tables classes Catalyst-specific, so you can still use them in a non-Catalyst context.

This module can be used almost as a drop-in replacement for CGI.pm for those of you who do not use the HTML generating features of CGI.pm This module provides an object-oriented interface for retrieving information provided by the Common Gateway Interface, as well as url-encoding and decoding values, and parsing CGI parameters.

*** WARNING *** THIS MODULE IS STILL EXPERIMENTAL !!! This module is related to the possible transition of Catalyst from NEXT to Class::C3. This transition hasn't happened yet, and might not for a while. This module is only intended for use by Catalyst module developers at this time. You would know it if you should be using this module. *** END WARNING ***

Catalyst::TraitFor::Controller::DBIC::DoesPaging - Helps you paginate, search, sort, and more easily using DBIx::Class. This module helps you to map various DBIx::Class features to CGI parameters. For the most part that means it will help you search, sort, and paginate with a minimum of effort and thought.

This view generates RRD graph images from the graph defintion placed in the stash. The controller is responsable of placing an ARRAYREF in $c-stash->{'graph'}> with the same data as to generate a graph with the RRDs module, except for filename, that will be automatically generated by the view.

Adds a Catalyst::Component "COMPONENT" method to your Catalyst component base class. This method reads the optional traits parameter from app and component config and instantiates the component subclass with those traits using "new_with_traits" in MooseX::Traits from MooseX::Traits::Pluggable.

CatalystX::InjectComponent will inject Controller, Model, and View components into your Catalyst application at setup (run)time. It does this by creating a new package on-the-fly, having that package extend the given component, and then having Catalyst setup the new component (via ->setup_component)

This module helps manage FCGI based web applications by providing a wrapper which handles most of the low-level FCGI details for you. It can run FCGI programs as simple scripts or as full standalone socket based servers who are managed by FCGI::Engine::ProcManager.

FCGI::ProcManager is used to serve as a FastCGI process manager. By re-implementing it in perl, developers can more finely tune performance in their web applications, and can take advantage of copy-on-write semantics prevalent in UNIX kernel process management. The process manager should be invoked before the caller''s request loop

PSGI/Plack is where it's at. Dancer's routing syntax is really cool, but it does a lot of things I don't usually want. What I really want is Dancer-like sugar as an extremely thin layer over my teeth^H^H^H^H^H PSGI apps.