view release on metacpan or search on metacpan
lib/Apache/DefaultCharset.pm view on Meta::CPAN
=head1 EXAMPLES
=head2 Unicode Handling
Suppose you develop multi-language web application, and transparently
decode native encodings into Unicode string inside Perl (5.8 or over
would be better). First you should add
AddDefaultCharset euc-jp
view release on metacpan or search on metacpan
Dynagzip.pm view on Meta::CPAN
I have to serve the POST requests for CGI binary with special care,
because in this case the handler
is standing along and have to serve all data flow in both directions
at the time when C<stdin> is tied into
Apache, and could not be exposed to CGI binary transparently.
To solve the problem I alter POST with GET request internally
doing the required incoming data transformations on the fly.
This could cause a problem, when you have a huge incoming stream from your client (more than 4K bytes).
view release on metacpan or search on metacpan
lib/Apache/GD/Graph.pm view on Meta::CPAN
graphs go, but YMMV.
=item B<background_image>
Set an image as the background for the graph. You are responsible for choosing
a sane image to go with your graph, the background should be either transparent
or the same color you will use. This is the same as using the C<logo> parameter
with an image of the same size as the graph, except this option will resize the
image if necessary, making it more convenient for this purpose. The file or URL
can be of any type your copy of GD supports.
view release on metacpan or search on metacpan
lib/Apache/Gallery.pm view on Meta::CPAN
Defaults to '0'.
=item B<GalleryCopyrightImage>
Image you want to blend into your images in the lower right
corner. This could be a transparent png saying "copyright
my name 2001".
Optional.
=item B<GalleryWrapNavigation>
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
],
[
['Time::HiRes' => 'For measuring rquest processing time' ],
['DBI 1.20' => 'Used in conjunction with Apache::Session::MySQL'],
['Apache::Filter' => 'JAF is filter-aware'],
['Apache::Session::MySQL' => 'Used for transparent session handling'],
],
],
[ 'JAF',
[
['5.6.0' => 'Perl 5.6.0 required'],
view release on metacpan or search on metacpan
Language.pod view on Meta::CPAN
=head1 NAME
Apache::Language - Perl transparent language support for Apache modules and mod_perl scripts
=head1 SYNOPSIS
In YourModule.pm:
Language.pod view on Meta::CPAN
previous release. It's still backward-compatible with the other releases, but
now it's much more advanced.
An Apache::Language object acts like a language-aware hash. It stores key/language/values
triplets. Using the Accept-Language: field sent by the web-client, it can pick the best
fit language for that specific client. It's usage is transparent and should prove
to be quite convenient (and hopefully, efficient).
The method used to store/fetch information is now completely modular and will allow
easy creation of new storage methods thru a simple API (see the API section).
view release on metacpan or search on metacpan
MIMEMapper.pm view on Meta::CPAN
requested resource. This means that you can now have .pl
scripts under htdocs/ (or wherever) without resorting to a
<Files> based configuration.
Apache::MIMEMapper also adds the ability to stack PerlHandlers
transparently using Apache::Filter. Handlers are added to the
PerlHandler stack in the order they appear in the httpd.conf file -
PerlSetVar Filter On is set if more than one extension is associated
with a specific Perl module.
=head1 EXAMPLE
view release on metacpan or search on metacpan
apache_mp3/apache_mp3.css view on Meta::CPAN
vertical-align: middle;
}
P {
/* font-family: sans-serif; */
background-color: transparent;
}
A {
/* font-family: sans-serif; */
background-color: transparent;
}
INPUT {
/* font-family: sans-serif; */
background-color: white;
apache_mp3/apache_mp3.css view on Meta::CPAN
.playlist {
background-color: #FFE89B;
}
A.playlist {
/* font-style: italic; */
background-color: transparent;
}
view release on metacpan or search on metacpan
migration/README view on Meta::CPAN
Migration from 1.11 to 1.12
1. It is important to note that if PageKit runs in a perl 5.6.x environment
all internal pages are in default_output_charset. For perl 5.8.x
all these pages are in perl's own unicode format. This change should
be transparent to the user but many libraries do not support perl's
new character handling.
=============================================================
Migration from 1.10 to 1.11
view release on metacpan or search on metacpan
lib/Apache/Pod/HTML.pm view on Meta::CPAN
border-width: 0;
color: inherit;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
PRE {
background: #eeeeee;
lib/Apache/Pod/HTML.pm view on Meta::CPAN
padding-bottom: 1em;
white-space: pre;
}
H1 {
background: transparent;
color: #006699;
font-size: x-large;
font-family: tahoma,sans-serif;
}
H2 {
background: transparent;
color: #006699;
font-size: large;
font-family: tahoma,sans-serif;
}
.block {
background: transparent;
}
TD .block {
color: #006699;
background: #dddddd;
view release on metacpan or search on metacpan
PrettyPerl.pm view on Meta::CPAN
$retval .= <<EOF;
a
{
color: $temp;
background-color: transparent;
text-decoration: none;
font-weight: bold;
}
a:hover
PrettyPerl.pm view on Meta::CPAN
$retval .= <<EOF;
span.comment
{
color: $temp;
background-color: transparent;
}
span.error
{
color: red;
PrettyPerl.pm view on Meta::CPAN
$retval .= <<EOF;
span.$_
{
color: $temp;
background-color: transparent;
}
EOF
}
$retval .= <<EOF;
view release on metacpan or search on metacpan
</Location>
=head1 DESCRIPTION
I<Apache::Request::I18N> adds transparent support over I<Apache::Request> for
internationalized GET/POST parameters. Form field names and values are
automatically decoded and converted either to Perl's internal UTF-8 format, or
to another character encoding.
Since this module inherits from I<Apache::Request>, it can be used as a
view release on metacpan or search on metacpan
lib/Apache/SdnFw/js/controls.js view on Meta::CPAN
}
if (this.options.externalControl)
this.options.externalControl = $(this.options.externalControl);
if (!this.options.externalControl)
this.options.externalControlOnly = false;
this._originalBackground = this.element.getStyle('background-color') || 'transparent';
this.element.title = this.options.clickToEditText;
this._boundCancelHandler = this.handleFormCancellation.bind(this);
this._boundComplete = (this.options.onComplete || Prototype.emptyFunction).bind(this);
this._boundFailureHandler = this.handleAJAXFailure.bind(this);
this._boundSubmitHandler = this.handleFormSubmission.bind(this);
view release on metacpan or search on metacpan
A session idle for the specified number of minutes will time out.
renewRate => <minutes>
A session which is constantly active will have a transparent
renewal (resetting an implicit 'idle timer') every period of the
specified number of minutes.
=head2 Quality of Protection Arguments
view release on metacpan or search on metacpan
CGI and other web servers, and it also works outside of a web server
altogether.
Apache::Session::Lazy extends Apache::Session by opening Sessions only after they are either
modified or examined (first read or write access to the tied hash.) It should provide
transparent access to the session hash at all times.
=head2 Uses Of Apache::Session::Lazy
Apache::Session::Lazy was designed to allow Apache::Session to achieve prevent unnecessary work
in accessing the data store, if a session is not going to be touched, and allow for session locking
view release on metacpan or search on metacpan
SessionManager/cookpod.pod view on Meta::CPAN
wrapper around L<Apache::Session|Apache::Session>
(L<Apache::Session|Apache::Session> provides a persistence mechanism for data
associated with a session between a client and the server).
L<Apache::SessionManager|Apache::SessionManager> allows you to integrate a
transparent session management into your web application (it handles for you
the cookie/URI session tracking management).
A session is a set of interactions (HTTP transactions). For example, a visitor
may add items to be purchased to a shopping cart and the contents of the cart
may be made visible by several different pages the visitor views during the
SessionManager/cookpod.pod view on Meta::CPAN
than 1024 and configure directly your F<httpd.conf>. Then you could ask to your
Webmaster in order to proxy your Apache from main web server (at port 80), if
you dont want export to the world a web site in a port different than 80.
So, working with F<.htaccess> files is the only possibilty to enable and
configure session manager transparently (both for web users and your
sysadmin).
Depending on wich Apache directives you would override, first you must check
the status of C<AllowOverride> directive for your directories.
SessionManager/cookpod.pod view on Meta::CPAN
connections offered by L<Apache::DBI|Apache::DBI> when using
L<Apache::SessionManager|Apache::SessionManager> with a RDBMS as session
datastore.
L<Apache::DBI|Apache::DBI> overrides DBI C<connect> and C<disconnect> methods
and it intercepts, transparently, all related calls (including
L<Apache::SessionManager|Apache::SessionManager> DBI calls) by returning cached
connections, if any.
Simply add a line like:
view release on metacpan or search on metacpan
SetWWWTheme.pm view on Meta::CPAN
=item @BLANKGIF
Server configuration only
This tag is used to specify the location of the blank.gif image file.
This image is a 1x1 transparent gif that is used to space the tables
properly. This should be set to the path of the image file with respect
to the server's document root. So, if the apache document root is /WWW
and the file is /WWW/images/blank.gif then the proper use of this tag
would be:
view release on metacpan or search on metacpan
lib/Apache/TestRun.pm view on Meta::CPAN
# XXX: do we care to check success?
system $cleanup_cmd;
# XXX: I tried hard to accomplish that w/o starting a new process,
# but too many things get on the way, so for now just keep it as an
# external process, as it's absolutely transparent to the normal
# app-run
}
my @oh = qw(jeez golly gosh darn shucks dangit rats nuts dangnabit crap);
sub oh {
view release on metacpan or search on metacpan
Apache::Throttle - Apache/Perl module for speed-based content negotiation
Apache::Throttle is a package designed to allow Apache webservers to
negotiate content based on the speed of the connection.
It's primary purpose is to transparently send smaller (lower
resolution/quality) images to users with slow internet connections,
but it can also be used for many other purposes.
Prerequisites:
* Apache w/ mod_perl
view release on metacpan or search on metacpan
The hit and byte total information is stored in shared memory to
minimize processing. On the first request of each day, all
previous data in shared memory is automatically moved to permanent
storage. This means that no more than one day's worth of information
is ever stored in shared memory, and prevents performance degradation
as data accumulates. This separation of data is transparent from
the end-user perspective.
If you would rather not have the data moved into the dbm file, you
can set USE_DBM to 0 at the top of the Traffic.pm module and reinstall.
view release on metacpan or search on metacpan
lib/Apache/UploadMeter/Resources/JavaScript.pm view on Meta::CPAN
} else this.style = $H(options.style)
this.start(options);
},
setup: function(){
function parseColor(color){
if(!color || ['rgba(0, 0, 0, 0)','transparent'].include(color)) color = '#ffffff';
color = color.parseColor();
return $R(0,2).map(function(i){
return parseInt( color.slice(i*2+1,i*2+3), 16 )
});
}
view release on metacpan or search on metacpan
VimColor.pm view on Meta::CPAN
<title>$filename_without_path</title>
HEADER
$req->print ($options->{'cssfile'} ? qq(\t\t<link rel="stylesheet" type="text/css" href=") . $options->{'cssfile'} . qq(" />\n) : <<HEADER);
<style type="text/css">
<!--
a { color: inherit; background-color: transparent; }
body { background-color: black; color: white; }
div.fixed { border: 1px solid silver; font-family: monospace; padding: 1ex; }
div.notice { color: silver; background-color: inherit; font-size: smaller; text-align: right; }
h1 { font-size: medium; }
span.linenumber { white-space: pre; color: yellow; background-color: transparent; }
span.Comment { color: blue; background-color: transparent; }
span.Constant { color: red; background-color: transparent; }
span.Identifier { color: aqua; background-color: transparent; }
span.Statement { color: yellow; background-color: transparent; }
span.PreProc { color: fuchsia; background-color: transparent; }
span.Type { color: lime; background-color: transparent; }
span.Special { color: fuchsia; background-color: transparent; }
span.Underlined { color: fuchsia; background-color: transparent; text-decoration: underline; }
span.Error { background-color: red; color: white; font-weight: bold; }
span.Todo { background-color: yellow; color: black; }
-->
</style>
HEADER
view release on metacpan or search on metacpan
Wyrd/Chart.pm view on Meta::CPAN
=item b_margin t_margin l_margin r_margin
edge-to-graphic margins
=item transparent interlaced
PNG options
=item bgclr fgclr boxclr textclr labelclr axislabelclr legendclr valuesclr
accentclr shadowclr
Wyrd/Chart.pm view on Meta::CPAN
sub _setup {
my ($self) = @_;
$self->{'_valid_attributes'} = {
'img' => [qw(align alt border height hspace ismap longdesc usemap vspace width src)],
'all' => [qw(b_margin t_margin l_margin r_margin transparent interlaced bgclr fgclr boxclr textclr labelclr axislabelclr legendclr valuesclr accentclr shadowclr dclrs show_values values_vertical values_space values_format logo logo_position logo_...
'axes' => [qw(x_label y_label box_axis two_axes zero_axis zero_axis_only x_plot_values y_plot_values y_max_value y_min_value x_tick_number x_min_value x_tick_number x_min_value x_max_value y_number_format x_label_skip y_label_skip x_tick_offset x...
'bars' => [qw(overwrite bar_width bar_spacing shadow_depth borderclrs cycle_clrs cumulate)],
'lines' => [qw(line_types line_type_scale line_width skip_undef)],
'points' => [qw(markers marker_size)],
'pie' => [qw(3d pie_height start_angle suppress_angle)],
'builtin_fonts' => [qw(gdTinyFont gdSmallFont gdMediumBoldFont gdLargeFont gdGiantFont)],
'font_attr' => [qw(legend_font title_font x_label_font y_label_font x_axis_font y_axis_font)],
'font_attr_pie' => [qw(legend_font title_font label_font value_font)],
'color_attr' => [qw(bgclr fgclr boxclr textclr labelclr axislabelclr legendclr valuesclr accentclr shadowclr dclrs)],
'array_attr' => [qw(dclrs markers)],
'boolean_attr' => [qw(transparent interlaced show_values values_vertical box_axis two_axes zero_axis zero_axis_only x_plot_values y_plot_values x_all_ticks x_labels_vertical long_ticks x_ticks correct_width cycle_clrs cumulate skip_undef 3d)]
};
$self->{'_chart_attributes'} = [];
$self->_set_default_attributes;
}
view release on metacpan or search on metacpan
man/xppcache.pod view on Meta::CPAN
and Expiry modules to XPP.
=head1 Store Modules
Store modules provide XPP with a way to store cache data. The way in which this
data is stored is up to the module, and is fairly transparent to the XPP code
wishing to cache the data. Here are the methods that need to be in every Store
module for things to work:
=head2 REQUIRED METHODS
view release on metacpan or search on metacpan
lib/Apache/forks.pm view on Meta::CPAN
# Configuration in httpd.conf
PerlModule Apache::forks # this should come before all other modules!
Do NOT change anything in your scripts. The usage of this module is transparent.
=head1 DESCRIPTION
Transparent Apache ithreads integration using forks. This module enables the
ithreads API to be used among multiple processes in a pre-forking Apache http
view release on metacpan or search on metacpan
sbin/asphelper view on Meta::CPAN
.required {
border-right: solid 6px #FF0000;
}
.optional {
border-right: solid 6px transparent;
}
</style>
</head>
<body>
<form method="post" action="/handlers/examples.contact">
view release on metacpan or search on metacpan
lib/Apache2/AuthCASpbh.pm view on Meta::CPAN
=head1 DESCRIPTION
AuthCASpbh is a framework for integrating CAS SSO support into the Apache web
server using mod_perl. It can authenticate Apache resources via CAS, perform
authorization via CAS attributes, acquire proxy granting tickets, and provides
a client allowing transparent access to other CAS applications via proxy
authentication. It automatically manages sessions using Apache::Session
(currently via sqlite, but other mechanisms could be used) and provides
mod_perl based applications access to session state and attributes.
=head2 Configuration options
view release on metacpan or search on metacpan
lib/Apache2/Controller/Directives.pm view on Meta::CPAN
Idle timeout in seconds, +2m, +3h, +4D, +6M, +7Y, or 'no timeout'.
Default is 1 hour. A month is actually 30 days, a year 365.
If you use 'no timeout' then logins will never expire.
This probably is not a good idea because OpenID url's can
be revoked, and because the login process can be a transparent
series of redirects if the user has something like
Verisign's SeatBelt plugin.
If you're doing some sort of cluster application or load balancing
and sharing the session between servers, make sure all your servers
view release on metacpan or search on metacpan
lib/Apache2/EmbedMP3/Template.pm view on Meta::CPAN
<param
name="menu" value="false">
<param
name="wmode" value="transparent">
</object>
EOF
view release on metacpan or search on metacpan
lib/Apache2/Filter/GoogleAnalytics.pm view on Meta::CPAN
PerlOutputFilterHandler Apache2::Filter::GoogleAnalytics
</Location>
=head1 DESCRIPTION
This module transparently adds a Google Analytics service scriptlet to each
HTML document that Apache httpd serves. It behaves asynchronous pass-thru
filter, thus its impact on performance is minimal.
=head1 OPTIONS