ANNOUNCE: MasonX::WebApp 0.01
Dave Rolsky <[email protected]> Tue, 11 May 2004 23:44:19 -0500 (CDT)
| Newsgroups | gmane.comp.web.mason.announce,gmane.comp.web.mason.user |
|---|---|
| Message-ID | <[email protected]> |
This is the first release of this code, and it's probably buggy, but I
think it's pretty neat.
From the docs ...
=head1 SYNOPSIS
# Create a subclass of MasonX::WebApp
package My::WebApp;
use base 'MasonX::WebApp';
sub _init
{
# do neat stuff
}
# In your Apache config file
<Location />
SetHandler perl-script
PerlHandler My::WebApp
</Location>
=head1 DESCRIPTION
C<MasonX::WebApp> works with Mason to let you do processing I<before>
Mason is ever invoked. There are a number of things that one might
want to do:
=over 4
=item * Argument munging
You might want to make sure all incoming arguments are UTF-8 encoded.
Or you might want to create some objects which Mason will see as
incoming arguments. For example, a "user_id" parameter could be
turned into a user object.
=item * Handle requests without Mason
If you're not generating output for the browser other than a redirect,
then there's no reason to use Mason. You can use a C<MasonX::WebApp>
subclass to handle all form submissions, for example.
This has the added benefit of making it easier to preload this code
once during server startup.
=item * Authorization checks
Why do authorization checks in Mason if a failed check just leads to a
redirect or NOT FOUND return code?
=back
-dave
/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3