This documentation is for the OpenInteract Apache content handler. For general information about OpenInteract, see OpenInteract::Intro. This content handler creates the OpenInteract::Request object and farms requests out to all the relevant handlers ...

No, we do not subclass DBI with this. No, we do not override any of the DBI methods. Instead, we provide the means to connect to the database from one location along with the ability to manipulate the default connection information before we connect....

This class/interface is responsible for authenticating users to the system and other authentication checks. If you have custom authentication needs you can specify your class in the server configuration and create your own or subclass this class and ...

Connect and/or bind to an LDAP directory....

This class provides a central location for error messages from all Interact modules. The error information collected in these variables is guaranteed to result from the most recent error generated by Interact....

This class is the base class for different caching implementations, which are themselves just wrappers around various CPAN modules which do the actual work. As a result, the module is pretty simple. The only tricky aspect is that we use this for cach...

Here we provide some common operations within OpenInteract that are not implmented within the data abstraction layer itself. Since we want to continue using both separately we cannot embed ideas like a configuration object or a particular cache imple...

Allows you to embed a configuration object that responds to get/set requests. Different from just using key/value pairs within your object since you do not have to worry about writing get/set methods, cluttering up your AUTOLOAD routine, or things li...

Install all the modules needed for OpenInteract. A few of them have to do with the package installer, but most are just for normal operation....

This module defines actions to be performed on individual packages. The first argument for many of the methods that...

The Request object is fairly simple, having only a few methods to it. But it really ties applications together in the OpenInteract framework, acting as an object repository, a layer between your object names and their classes, and as a data store bet...

This class currently implments utilities for sending email. Note: In the future the mailing methods may move into a separate class (e.g., "OpenInteract::Mailer")...

This module has a number of routines that are (hopefully) independent of the OpenInteract implementation. One of its primary goals is to make it simple to initialize OpenInteract not only in a mod_perl context but also a single-use context. For examp...

Sessions are a fundamental part of OpenInteract, and therefore session handling is fairly transparent. We rely on Apache::Session to do the heavy-lifting for us. This handler has two public methods: "parse()" and "save()". Guess in which order they a...

A Component can be called from either a 'Static' page, from a template, or from anything else in the system. from another content handler. A component is called the same either way: my $html = OpenInteract::Component->handler( $action, \%params ) my ...

One of the difficulties with developing an application that can potentially work with so many different databases is that it needs to work with so many different databases. Many of the differences among databases are dealt with by the amazing DBI mod...

Note: This class template is used when generating a new website via 'oi_manage' and is not meant to be used directly. The existence of the 'stash class' is necessitated by the fact that we can have more than one application running at the same time. ...

This class implements most of the common functionality required for finding and displaying multiple objects, viewing a particular object, making changes to it and removing it. And you just need to modify a few configuration methods so that it knows w...

"OpenInteract::ApacheStartup" should be run from the startup.pl file of your website. (You can probably also load it directly from your apache config as well, but we will stick with simple things for now :) Its purpose is to load as many modules as p...

This is a different type of module than many others in the "OpenInteract::" hierarchy. Instead of being created from scratch, the configuration information is in the class rather than in a configuration file. It does not use a SQL database for a back...