Results 1,011–1,020 of 8,048 for /www/.(0.005 seconds)
Document Object Model for Cascading Style Sheets
This module provides the CSS-specific interfaces described in the W3C
DOM recommendation.
The CSS::DOM class itself implements the StyleSheet and CSSStyleSheet
DOM interfaces.
Library for converting CSS blocks and files to inline styles
Library for converting CSS <style> blocks and external CSS files to inline
styles.
Automated REST Method Dispatching for Catalyst
Catalyst::Controller::REST implements a mechanism for building RESTful
services in Catalyst. It does this by extending the normal Catalyst
dispatch mechanism to allow for different subroutines to be called based
on the HTTP Method requested, while also transparently handling all the
serialization/deserialization for you.
Sensible default end action for Catalyst
This action implements a sensible default end action, which will forward
to the first available view, unless status is set to 3xx, or there is a
response body. It also allows you to pass "dump_info=1" to the url in
order to force a debug screen, while in debug mode.
If you have more than one view, you can specify which one to use with
the "default_view" config setting (see ""$c->view($name)" in "Catalyst".)
XML::Hash::LX serializer for Catalyst::Action::Serialize
XML::Hash::LX serialize/deserializer for Catalyst (Catalyst::Action::Serialize
and Catalyst::Action::Deserialize).
User role-based authorization action class
Provides a Catalyst reusable action role for user role-based authorization.
ACLs are applied via the assignment of attributes to application action
subroutines.
HTTP plain and digest authentication plugin for Catalyst
OpenID credential for Catalyst::Plugin::Authentication framework
OpenID credential for Catalyst::Plugin::Authentication framework.
Storage class for Catalyst Authentication using DBIx::Class
A storage class for Catalyst Authentication using DBIx::Class
Authentication from an LDAP Directory for Catalyst
This plugin implements the Catalyst::Authentication v.10 API.
This plugin uses Net::LDAP to let your application authenticate against
an LDAP directory. It has a pretty high degree of flexibility, given
the wide variation of LDAP directories and schemas from one system to
another.
It authenticates users in two steps:
1) A search of the directory is performed, looking for a user object
that matches the username you pass. This is done with the bind
credentials supplied in the "binddn" and "bindpw" configuration options.
2) If that object is found, we then re-bind to the directory as that
object. Assuming this is successful, the user is Authenticated.