Free pluggable software for linux

WWW::Mechanize::Pluggable provides all of the same functionality of WWW::Mechanize, but adds support for plugins using Module::Pluggable; this means that any module named WWW::Mechanize::Plugin::whatever... will be found and loaded when WWW::Mechanize::Pluggable is loaded.

Big deal, you say. Well, it becomes a big deal in conjunction with WWW::Mechanize::Pluggables other feature: plugin hooks. When plugins are loaded, their import() methods can call WWW::Mechanize::Pluggables prehook and posthook methods. These methods add callbacks to the plugin code in WWW::Mechanize::Pluggables methods. These callbacks can act before a method or after it, and have to option of short-circuiting the call to the WWW::Mechanize::Pluggable method altogether.

These methods receive whatever parameters the WWW::Mechanize::Pluggable methods received, plus a reference to the actvive Mech object.

All other extensions to WWW::Mechanize::Pluggable are handled by the plugins.

SUBCLASSING

Subclassing this class is not recommended; partly because the method redispatch we need to do internally doesnt play well with the standard Perl OO model, and partly because you should be using plugins and hooks instead.

In WWW::Mechanize, it is recommended that you extend functionality by subclassing WWW::Mechanize, because theres no other way to extend the class. With Module::Pluggable support, it is easy to load another method directly into WWW::Mechanize::Pluggables namespace; it then appears as if it had always been there. In addition, the pre_hook() and post_hook() methods provide a way to intercept a call and replace it with your output, or to tack on further processing at the end of a standard method (or even a plugin!).

The advantage of this is in not having a large number of subclasses, all of which add or alter WWW::Mechanizes function, and all of which have to be loaded if you want them available in your code. With WWW::Mechanize::Pluggable, one simply installs the desired plugins and they are all automatically available when you use WWW::Mechanize::Pluggable.

Configuration is a possible problem area; if three different plugins all attempt to replace get(), only one will win. Its better to create more sophisticated methods that call on lower-level ones than to alter existing known behavior.

Bot::BasicBot::Pluggable::Module::Google is an extension to the simple irc bot base class allowing for pluggable modules.

SYNOPSIS

Googles for things

IRC USAGE

Commands:

google < terms >

Returns google hits for the terms given

spell

Returns a google spelling suggestion for the words given

VARS

google_key

The google API key to use for lookups. Must be set to use the module. The easiest way to do this is to use the Vars module and tell the bot

!set Google google_key < key >

JGlade is a reimplementation of libglade in pure Java that enables Glade UI designs to be ported to platform independent toolkits, like SWT and Eclipse.

Toolkits are managed through an Abstract factory, and pluggable modules supporting other toolkits can be implemented.

Glade UI designer produces an XML file describing the interface in GTK+ terms, this file is parsed by JGlade and a new SWT interface is constructed making the necessary conversion from GTK+ to SWT or other toolkit.

WWW::Mechanize::Plugin::Cache is an automatic request caching for WWW::Mechanize::Pluggable.

SYNOPSIS

# With this plugin installed:
use WWW::Mechanize::Pluggable;
my $cached_mech = new WWW::Mechanize::Pluggable new_cache=>1;
$mech->get("http://yahoo.com"); # Fetched from Web
$mech->get("http://yahoo.com"); # Fetched from cache

# To use an old cache:
my $cache = Cache::FileCache->new(cache_root=>/old/cache/root);
my $cached_mech = new WWW::Mechanize::Pluggable cache=>$cache;
$mech->get("http://yahoo.com"); # Fetched from the old cache

This plugin adds caching functionality to WWW::Mechanize::Pluggable. It duplicates the functionality of WWW::Mechanize::Cached; you can have WWW::Mechanize::Pluggable set up the cache for you, or reuse a previously-filled cache.

The pam_ccreds module provides the means for Linux workstations to locally authenticate using an enterprise identity when the network is unavailable. Used in conjunction with the nss_updatedb utility, it provides a mechanism for disconnected use of network directories. They are designed to work with pam_ldap and nss_ldap, also available from PADL.
Here are some benefits of using pam_ccreds:
Uses the Pluggable Authentication Module API defined in OSF DCE RFC 86.0 (with Linux-PAM extensions)
Supports any PAM authentication module
Secure cached credentials provides for verification only
The pam_ccache module supports Linux only.
The present implementation requires Linux-PAM as it takes advantage of the extended configuration syntax of pam.conf. (See the example configuration file included with the
software for an example of configuring it with pam_ldap.) On platforms that do not use Linux-PAM you would need a wrapper PAM module to choose an action based on the
previous modules return code.
Enhancements:
- build fix (include syslog.h)

XTAS provides a Java library for XML.
XTAS (XML Transformation And Storing) XML Java API aimed to *manipulation* XML data from both: non-persistent source that can be generated programmatically (Java stream, DOM, Mapped Java-Object for instance) and persistent source that can be retrieved/stored in/from some XML-enabled "Resource" (XML file or XML enabled DB for instance) with or without validation rules, locally or remotely.
Main features:
- Simple yet powerful XML selection/modification API.
- XSLT/Xpath based query engine.
- Querying both persistent(Resource) and not persistent(generated programmatically) XML sources.
- Pluggable Resources
- XML Validation supporting
- Java Object/XML mapping, [un]marshalling
- Local and Client/Server environment

pam_require is a simple Pluggable Authentication Module (PAM) for Linux (and maybe other systems which use PAM).
pam_require is an account module that allows you to require a special user or group to access a service.
Example
/etc/pam.d/ssh:
auth required pam_nologin.so
auth required pam_unix.so
auth required pam_env.so
account required pam_unix.so
account required pam_require.so @ssh-users admin
session required pam_unix.so
session optional pam_lastlog.so
session optional pam_motd.so
session optional pam_mail.so standard noenv
session required pam_limits.so
password required pam_unix.so
The above example requires a user to be member of the group ssh-users or to be user admin himself to login via ssh.
Enhancements:
- This release adds the ability to do non-case-sensitive matches, and fixes how negations are handled.