Free apache 2.0.63 software for linux

Apache::ePerl is a fast emulated Embedded Perl (ePerl) facility.

SYNOPSIS

# Apaches httpd.conf file
# mandatory: activation of Apache::ePerl
PerlModule Apache::ePerl
< Files ~ "/root/of/webmaster/area/.+.iphtml$" >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::ePerl
< /Files >
# optional: configuration of Apache::ePerl
< Perl >
$Apache::ePerl::Config->{BeginDelimiter} = $Apache::ePerl::Config->{EndDelimiter} = !>;
$Apache::ePerl::Config->{CaseDelimiters} = 0;
$Apache::ePerl::Config->{ConvertEntities} = 1;
< /Perl >
# optional: activation of Apache::Status for Apache::ePerl
< Location /perl-status >
Options +ExecCGI
SetHandler perl-script
PerlHandler Apache::Status
< /Location >

This packages provides a handler function for Apache/mod_perl which can be used to emulate the stand-alone Server-Side-Scripting-Language ePerl (see eperl(3) for more details) in a very fast way. This is not a real 100% replacement for nph-eperl because of reduced functionality under some special cases, principal runtime restrictions and speedup decisions. For instance this variant does not (and cannot) provide the SetUID feature of ePerl nor does it check for allowed filename extensions (speedup!), etc. Instead it uses further features like object caching which ePerl does not use.

But the accepted bristled source file format is exactly the same as with the regular ePerl facility, because Apache::ePerl uses the Parse::ePerl package which provides the original ePerl parser and translator. So, any valid ePerl which works under nph-eperl can also be used under Apache::ePerl.

The intent is to use this special variant of ePerl for scripts which are directly under control of the webmaster. In this situation no real security problems exists for him, because all risk is at his own hands. For the average user you should not use Apache::ePerl. Instead additionally install the regular stand-alone ePerl facility (nph-eperl) for those users.

So, the advantage of Apache::ePerl against the regular nph-eperl is better performance and nothing else. Actually scripts executed under Apache::ePerl are at least twice as fast as under nph-eperl. The reason its not that ePerl itself is faster. The reason is the runtime in-core environment of Apache/mod_perl which does not have any forking overhead.

Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java.
Apache Lucene is a technology suitable for nearly any application that requires full-text search, especially cross-platform.
Enhancements:
- Many new features, optimizations, and bugfixes have been added since 2.1.0, including "point-in-time" searching over NFS, payloads, function queries, and new APIs for pre-analyzed fields.
- This release includes index format changes that are not readable by older versions.
- It can both read and update older Lucene indexes.
- Adding to an index with an older format will cause it to be converted to the newer format.

Nutch project is Web searching software which builds on Lucene Java, adding Web specifics such as a crawler, a link-graph database, parsers for HTML and other document formats, etc.
Interesting files include:
docs/api/index.html
Javadocs for the Nutch software.
CHANGES.txt
Log of changes to Nutch.
For the latest information about Nutch, please visit our website at:
http://lucene.apache.org/nutch/
and our wiki, at:
http://wiki.apache.org/nutch/
To get started using Nutch read Tutorial:
http://lucene.apache.org/nutch/tutorial.html
Enhancements:
- This release includes several critical bugfixes, as well as key speedups.

Apache Ant is a Java based build tool, similar to make, but with better support for the cross platform issues involved with developing Java applications.
Apache Ant is the build tool of choice for all Java projects at Apache and many other Open Source Java projects.
Enhancements:
- A resource framework was introduced.
- Some of the core ant tasks such as copy are now able to process not only file system resources but also zip entries, tar entries, and paths.
- Resource collections group resources, and can be further combined with operators such as union and intersection.
- This version starts outsourcing of optional tasks to Antlibs.
- The .NET antlib replaces the .NET optional tasks.
- Support for the version control system Subversion is also provided as an antlib.
- A large number of bugs were fixed.
- Some initial support for Java6 features was added.

Apache SNMP Module allows you to monitor different configuration and status values of the Apache Web server using SNMP.
Enhancements:
- Bugfixes, the inclusion of MRTG scripts, and changes to make the module work on the IBM HTTP Server.

Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development.

Apache Cocoon implements these concepts around the notion of component pipelines, each component on the pipeline specializing on a particular operation.

This makes it possible to use a Lego(tm)-like approach in building web solutions, hooking together components into pipelines without any required programming.

Apache Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of all aspects of a web application, improving development pace and reducing the chance of conflicts.

Apache::Wyrd is a Perl module for HTML embeddable perl objects under mod_perl.

Apache::Wyrd is the core module in a collection of interoperating modules that allow the rapid object-oriented development of web sites in Apaches mod_perl environment (LAMP). This collection includes a very flexible, HTML-friendly method of defining dynamic items on a web page, and interfacing directly to perl objects with them. It comes with many pre-built objects to support a web site such as an authentication module, an reverse-lookup database, granular debugging, and smart forms/inputs and their interfaces to a DBI-compliant SQL application.

The collection is not meant to be a drop-in replacement for PHP, ColdFusion, or other server-side parsed content creation systems, but to provide a more flexible framework for organic custom perl development for an experienced perl programmer who favors an object-oriented approach. It has been designed to simplify the transition from static to dynamic web content by allowing the design of objects that can be operated by a non-perl programmer through the modification of the HTML page on which the content is to be delivered.

The Apache::Wyrd module itself is an abstract class used to create HTML-embeddable perl objects (Wyrds). The embedded objects are interpreted from HTML files by an instance of the abstract class Apache::Wyrd::Handler. Most Wyrds also require an instance of an Apache::Wyrd::DBL object to store connection information and to provide intermediary access to the Apache request and any DBI-style database interfaces.
Each Wyrd has a corresponding perl module which performs work and generates output at the Wyrds location on the HTML page, if any. Each of these objects is a derived class of Apache::Wyrd, and consequently draws on the existing methods of the abstract class as well as implements methods of its own. A few "hook" methods (_setup, _format_output, and _generate_output in particular) are defined in the abstract class for this purpose.

The modules in this distribution are not meant to be used directly. Instead, instances of the objects are created in another namespace (in all POD synopses called BASENAME, but it can be any string acceptable as a single namespace of a perl class) where the Handler object has been configured to use that namespace in interpreting HTML pages (see Apache::Wyrd::Handler).