view release on metacpan or  search on metacpan

lib/Apache/BabyConnect.pm  view on Meta::CPAN

=head1 DESCRIPTION

This module initiates persistent database connections using DBI::BabyConnect.

This module is best understood by going through the roadmap file and the
sample programs provided with this distribution. The roadmap file is
eg/README, and the sample programs are in eg/perl.

When loading the Apache::BabyConnect module, the
module looks if the environment variable BABYCONNECT has been set to the

 view release on metacpan or  search on metacpan

Backhand.pm  view on Meta::CPAN

As explained above, you cannot PerlModule or use() or require()
Apache::Backhand until *after* mod_backhand (and mod_perl, of course) are
linked into the server.

As explained above, you cannot call load_serverstats() until *after* the
shared memory segment has been created and attached.  The best place to do
this is the child init phase.

It's easy to make mod_backhand coredump by doing Bad Things to serverstats
(e.g. 'foreach (@{$serverstats}) { $_->{'mtime'} = time() }'...)
Even though I've provided the magic to make serverstats writeable, this should

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

ChangeLog  view on Meta::CPAN

	* Makefile.PL: Added prerequisites, so that CPAN.pm and other
	installation tools will let you know if you need the latest
	versions of various modules.  Truth be told, I'm not sure what the
	minimum versions are for the required modules, so I just set them
	to the current values and will hope for the best.

	* CodeRed.pm: What didn't I do?  I wrote some POD, gave the module
	a new name (Apache::CodeRed, rather than plain ol' CodeRed),
	retooled a few basic things, removed some bugs.
	

 view release on metacpan or  search on metacpan

GPL  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

  USAGE
    Different to Apache::DBI Apache::DBI::Cache must be "use"ed not
    "require"ed. That means it's "import" function must be called.

    When used with mod_perl (versions 1.x or 2.x) this is best done in a
    "startup.pl" or in a "<Perl>" section in the "httpd.conf". See mod_perl
    documentation for more information.

    Thereafter, "DBI->connect" is called as usual. No special treatment is
    needed.

 view release on metacpan or  search on metacpan

DBILogin.pm  view on Meta::CPAN

The database user's clear text passwd is made available in the
server's environment. Do you trust your developers?

=head1 BUGS

Probably lots, I'm not the best programmer in the world.

=head1 NOTES

Feel free to email me with comments, suggestions, flames. Its the
only way I'll become a better programmer.

 view release on metacpan or  search on metacpan

Dynagzip.pm  view on Meta::CPAN

=over 4

=item Note:

Do your best in order to avoid the implementation of this handler in internally redirected requests.
It does not help much in this case. Read your C<error_log> carefully in order to find appropriate
warnings. Tune your C<httpd.conf> carefully in order to take the most from opportunities offered
by this handler.

Always use accomplishing C<Apache::CompressClientFixup> handler in order to avoid C<gzip> compression

 view release on metacpan or  search on metacpan

lib/Apache/ExtDirect.pm  view on Meta::CPAN

=head1 BUGS AND LIMITATIONS

Apache 1.x is not supported at this time.

There are no known bugs in this module. To report bugs, use github RT
(the best way) or just drop me an e-mail. Patches are welcome.

=head1 AUTHOR

Alexander Tokarev, E<lt>tokarev@cpan.orgE<gt>

 view release on metacpan or  search on metacpan

GPL  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least

 view release on metacpan or  search on metacpan

examples/ebay/FF4eBay-tmpl--v4.csv  view on Meta::CPAN

;"Einkaufswert ";;"\eor";;;;;;
;"eBay-Wert ";;"\eor";;;;;;
;"Differenz eBay-Wert minus Einkaufswert ";;"\eor";;;;;;
"\eor";;;;;;;;;
"\eor";"Angaben zu den einzelnen Produkten am Lager";;;;;;;;
"\eor";"eBay-Artikelnummer";"Beschreibung";"Lager- bestand in Stück";"Einkaufs- preis ";"Aktueller eBay Auktionspreis ";"Einkaufswert vom Lagerbestand";"Wert vom Lager- bestand nach eBay-Preis";"Differenz eBay minus Einkaufswert";
;;;;;;"\eor"
;;;;;;"\eor"
;;;;;;"\eor"
;;;;;;"\eor"
;;;;;;"\eor"

 view release on metacpan or  search on metacpan

FileManager.pm  view on Meta::CPAN

 #Add your own methods here

1;

The best way to subclass the filemanager would be to copy the methods you want 
to overload from the Apache::FileManager file to your new subclass. Then change
the methods to your liking.

=head1 BUGS

 view release on metacpan or  search on metacpan

Makefile.PL  view on Meta::CPAN

'NAME' => 'Apache::FilteringProxy',
'VERSION_FROM' => 'lib/Apache/FilteringProxy.pm',
'PREREQ_PM' => { LWP::UserAgent => 0,
                 XML::EasyOBJ => 0
			   },
'dist'          => { COMPRESS => 'gzip --best', SUFFIX => 'gz' },
'ABSTRACT_FROM' => 'lib/Apache/FilteringProxy.pm',
'AUTHOR' => 'David Castro <dcastro@apu.edu>',
);

 view release on metacpan or  search on metacpan

lib/Apache/GopherHandler.pm  view on Meta::CPAN

implementation details of the protocol.  Apache::GopherHandler provides the 
glue between that module and Apache.

=head1 CONFIGURATION

The best way to run Apache::GopherHandler is inside an Apache <VirtualHost>.  
Actual configuration is done either inside a <Perl> directive or your 
Apache startup file.  This is done by accessing the hash 
C<%Apache::GopherHandler::Config>.  Keys can be specified here that will 
be passed to the C<Gopher::Server::Requesthandler> you specify in the 
C<handler> key.  Currently, only C<Gopher::Server::RequestHandler::File> 

 view release on metacpan or  search on metacpan

lib/Apache/HTTunnel.pod  view on Meta::CPAN

in cases when the connection blocks, this directive limits the 
connection timeout that may be specified by the client.

  Ex: HTTunnelMaxConnectTimeout 10

The default value is 15 seconds. It is best to keep the value relatively
low to prevent blocking in the Apache child.

=item HTTunnelMaxReadTimeout

C<HTTunnel::Client> needs to poll to check if there is some data to be 

lib/Apache/HTTunnel.pod  view on Meta::CPAN

that take longer than HTTunnelReadTimeout seconds. A special response 
is sent to the client telling it to retry the read request.

  Ex: HTTunnelMaxReadTimeout    10

The default value is 15 seconds. It is best to keep the value relatively
low to prevent blocking in the Apache child.

=item HTTunnelMaxReadLength

The maximum number of bytes that a client may request for a read.

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

ppport.h  view on Meta::CPAN

#ifndef IVSIZE
#  ifdef LONGSIZE
#    define IVSIZE LONGSIZE
#  else
#    define IVSIZE 4 /* A bold guess, but the best we can make. */
#  endif
#endif
#ifndef UVTYPE
#  define UVTYPE                         unsigned IVTYPE
#endif

ppport.h  view on Meta::CPAN

#ifndef PERL_MAGIC_ext
#  define PERL_MAGIC_ext                 '~'
#endif

/* That's the best we can do... */
#ifndef SvPV_force_nomg
#  define SvPV_force_nomg                SvPV_force
#endif

#ifndef SvPV_nomg

 view release on metacpan or  search on metacpan

lib/Apache/JumpByReferer.pm  view on Meta::CPAN

=head1 TODO

* I should know how to use Apache::test for testing this module.

* I should know whether it's the best way to put the handler under
  C<PerlAccessHandler>.

* Probably, I should study English more to write the document neatly.

=head1 SEE ALSO

 view release on metacpan or  search on metacpan

lib/Apache/LangPrefCookie.pm  view on Meta::CPAN

        # inserting '*'.
        @ua_lang_prefs = q/*/;
    }

    # Now: unless the cookie wants a language that would be the
    # best matching anyway, rebuild the list of language-ranges
    unless ( $cookie_pref_lang eq $ua_lang_prefs[0] ) {
        my ( $qvalue, $language_ranges ) = ( 1, '' );
        map {
            if (m/^(?:\w{1,8}(?:-\w{1,8})*|\*)$/)
            {

lib/Apache/LangPrefCookie.pm  view on Meta::CPAN

choice. The original preferences are still present, albeit with lowered
q-values. The cookie's name is configurable, as described in the
examples. Setting/modifying/deleting such a cookie is to be handled
separately; F<Apache::LangPrefCookie> just consumes it.

After that, it's up to httpd's mod_negotiation to choose the best
deliverable representation.

=head2 WHY?

I had demands to let users switch language I<once> for a given site.

 view release on metacpan or  search on metacpan

LangURI.pm  view on Meta::CPAN

=head1 DESCRIPTION

Apache::LangURI will attempt to match the first segment of the path
of an http URL to an RFC3066 E<lt>majorE<gt>-E<lt>minorE<gt> language code.
It will also optionally prepend the "best" language code to the path, should
it not already be there. Language tags are normalized to a lower case major
with an upper case minor and a hyphen in between.

=head1 CONFIGURATION

 view release on metacpan or  search on metacpan

Language.pm  view on Meta::CPAN

    print "<PRE>";
    print Dumper $self;
    print "</PRE>";
    }

#given an ordered list of knowns languages, returns the best language 
#choice according to the client request
#Called mostly by LanguageHandlers to figure out what language to pick
sub best_lang {
    my ($self,@offered) = @_;
    my ($result, $language);

    $self = tied %$self if tied %$self;
    foreach my $want (@ {$self->{Lang}}) {

 view release on metacpan or  search on metacpan

Makefile  view on Meta::CPAN

# --- MakeMaker dist section:
TAR = COPY_EXTENDED_ATTRIBUTES_DISABLE=1 COPYFILE_DISABLE=1 tar
TARFLAGS = cvf
ZIP = zip
ZIPFLAGS = -r
COMPRESS = gzip --best
SUFFIX = .gz
SHAR = shar
PREOP = $(NOECHO) $(NOOP)
POSTOP = $(NOECHO) $(NOOP)
TO_UNIX = $(NOECHO) $(NOOP)
CI = ci -u
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q
DIST_CP = best
DIST_DEFAULT = tardist
DISTNAME = Apache-LoadAvgLimit
DISTVNAME = Apache-LoadAvgLimit-0.03_01

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

DBI.pm  view on Meta::CPAN

If you have questions about DBI, or DBD driver modules, you can get
help from the I<dbi-users@perl.org> mailing list.  You can get help
on subscribing and using the list by emailing I<dbi-users-help@perl.org>.

(To help you make the best use of the dbi-users mailing list,
and any other lists or forums you may use, I I<strongly>
recommend that you read "How To Ask Questions The Smart Way"
by Eric Raymond: L<http://www.catb.org/~esr/faqs/smart-questions.html>)

The DBI home page at L<http://dbi.perl.org/> is always worth a visit

DBI.pm  view on Meta::CPAN

my $dbd_prefix_registry = {
  ad_      => { class => 'DBD::AnyData',	},
  ado_     => { class => 'DBD::ADO',		},
  amzn_    => { class => 'DBD::Amazon',		},
  best_    => { class => 'DBD::BestWins',	},
  csv_     => { class => 'DBD::CSV',		},
  db2_     => { class => 'DBD::DB2',		},
  dbi_     => { class => 'DBI',			},
  dbm_     => { class => 'DBD::DBM',		},
  df_      => { class => 'DBD::DF',		},

DBI.pm  view on Meta::CPAN

    return $td;
}


# Help people doing DBI->errstr, might even document it one day
# XXX probably best moved to cheaper XS code
sub err    { $DBI::err    }
sub errstr { $DBI::errstr }


# --- Private Internal Function for Creating New DBI Handles

DBI.pm  view on Meta::CPAN

Returns a list of hash references holding information about one or more
variants of $data_type. The list is ordered by C<DATA_TYPE> first and
then by how closely each type maps to the corresponding ODBC SQL data
type, closest first.  If called in a scalar context then only the first
(best) element is returned.

If $data_type is undefined or C<SQL_ALL_TYPES>, then the list will
contain hashes for all data type variants supported by the database and driver.

If $data_type is an array reference then C<type_info> returns the

DBI.pm  view on Meta::CPAN

check the return value before trying to do other things with it in
your overridden method. This is especially important if you want
to set a hash attribute on the handle, as Perl's autovivification
will bite you by (in)conveniently creating an unblessed hashref,
which your method will then return with usually baffling results
later on.  It's best to check right after the call and return undef
immediately on error, just like DBI would and just like the example
above.

If your method needs to record an error it should call the set_err()
method with the error code and error string, as shown in the example

DBI.pm  view on Meta::CPAN

  3 - As above, adding some high-level information from the driver
      and some internal information from the DBI.
  4 - As above, adding more detailed information from the driver.
  5 to 15 - As above but with more and more obscure information.

Trace level 1 is best for a simple overview of what's happening.
Trace level 2 is a good choice for general purpose tracing.
Levels 3 and above are best reserved for investigating a specific
problem, when you need to see "inside" the driver and DBI.

The trace output is detailed and typically very useful. Much of the
trace output is formatted using the L</neat> function, so strings
in the trace output may be edited and truncated by that function.

 view release on metacpan or  search on metacpan

lib/Apache/Logmonster/Utility.pm  view on Meta::CPAN

  use Apache::Logmonster::Utility;
  my $toaster = Apache::Logmonster::Utility->new;

  $util->file_write($file, lines=> @lines);

This is just one of the many handy little methods I have amassed here. Rather than try to remember all of the best ways to code certain functions and then attempt to remember them, I have consolidated years of experience and countless references from...


=head1 DESCRIPTION

This Apache::Logmonster::Utility package is my most frequently used one. Each method has its own documentation but in general, all methods accept as input a hashref with at least one required argument and a number of optional arguments.

lib/Apache/Logmonster/Utility.pm  view on Meta::CPAN

Decompresses a variety of archive formats using your systems built in tools.

  ############### extract_archive ##################
  # Usage      : $util->extract_archive( 'example.tar.bz2' );
  # Purpose    : test the archiver, determine its contents, and then
  #              use the best available means to expand it.
  # Returns    : 0 - failure, 1 - success
  # Parameters : S - archive - a bz2, gz, or tgz file to decompress


=item cwd_source_dir

 view release on metacpan or  search on metacpan

Makefile.old  view on Meta::CPAN

POSTOP = @$(NOOP)
ZIP = zip
DIST_DEFAULT = tardist
CI = ci -u
SHAR = shar
COMPRESS = gzip --best
DIST_CP = best
PREOP = @$(NOOP)
TARFLAGS = cvf
DISTVNAME = $(DISTNAME)-$(VERSION)
SUFFIX = .gz
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q

 view release on metacpan or  search on metacpan

Makefile.PL  view on Meta::CPAN

	'DBI'			=> 1.21,
	'Apache::Request'	=> 1.0,
	'mod_perl'		=> 1.26
    	}, # e.g., Module::Name => 1.1
     dist		=> {
     	COMPRESS => 'gzip --force --best'
     	},
);

 view release on metacpan or  search on metacpan

License.GPL  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least