Free apache 16 software for linux

apache-top provides real-time display of the active processes from a remote apache server.
With apache-top you can get:
- The active apache processes with their associated PID, the status, the seconds being active, the CPU usage, the asociated VirtualHost, the accessing ip and the request (POST or GET, the file being accessed and the used protocol)
- The server uptime and the last time it was restarted
- The CPU usage
- Requests by second, Kb by second and the average Kb by request
- Number of active and inactive processes
- A graph with the inactive and active processes and their status

Apache Solr is a high performace search server based on Lucene, with XML/HTTP and JSON APIs, hit highlighting, faceted search, caching, replication, and a Web administration interface.
The project is currently under incubation at the Apache Software Foundation.
Instructions for Building Apache Solr
1. Download the J2SE 5.0 JDK (Java Development Kit) or later from http://java.sun.com. You will need the JDK installed, and the %JAVA_HOME%bin directory included on your command path. To test this, issue a "java -version" command from your shell and verify that the Java version is 5.0 or later.
2. Download the Apache Ant binary distribution from http://ant.apache.org. You will need Ant installed and the %ANT_HOME%bin directory included on your command path. To test this, issue a "ant -version" command from your shell and verify that Ant is available.
3. Download the Apache Solr source distribution, linked from the above incubator web site. Expand the distribution to a folder of your choice, e.g. c:solr.
4. Navigate to that folder and issue an "ant" command to see the available options for building, testing, and packaging solr.
Enhancements:
- This is the first release since graduating from the Apache Incubator.
- Some of the new features include CSV/delimited-text data loading, time based autocommit, faster faceting, negative filters, a spell-check handler, sounds-like word filters, regex text filters, and more flexible plugins.

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 Harmony is the Java SE project of the Apache Software Foundation. Please help us make this a world class, certified implementation of the Java Platform Standard Edition!

Apache Harmonys aim is to produce a large and healthy community of those interested in runtime platforms tasked with creation of :

A compatible, independent implementation of the Java SE 5 JDK under the Apache License v2.
A community-developed modular runtime (VM and class library) architecture.

We aim to support wide range of different platforms. The main criteria for whether a particular platform is supported or not is the involvement of people in running tests on regular base, reporting build status, finding and fixing bugs for that platform, and so on. We have a list of platforms we are actively maintaining at the moment.

Project Status

JRE and HDK snapshots available
JRE can run popular programs like Apache Tomcat, Eclipse, Maven, Derby, Ant
More than 95% of Java 5 API complete. (not compatible, just completed)
More than 1.25 Million Lines of Code

AntUnit is a library of Ant tasks that was initially developed to write tests for Ant tasks without resorting to JUnit. Apache AntUnit makes it easy to turn an existing build file that exhibits an error into an AntUnit test.

Tests are written as targets in a build file using assertion tasks provided by AntUnit. The antunit task executes targets in a collection of build files and supports custom listeners in a manner similar to the junit tasks formatters.

Apache::BioChrome is an Apache handler for Image::BioChrome to colorize gif files based on information provided in the url.

SYNOPSIS

#httpd.conf
PerlTransHandler Apache::BioChrome

# anywhere you can configure a location
< Location /biochrome >
PerlSetVar biochrome_cache /tmp/biochrome
PerlSetVar biochrome_source /usr/www/images/biochrome
< /Location >

This module is designed to allow the automatic building of gif images that make up an interface by using the Image::BioChrome module to replace values in the global color table. It takes the color information from the URL and creates a copy of the gif file from the source directory in the location specified by the biochrome cache variable. This file is then returned by apache using the standard delivery method.

I developed this module because we produce lots of web sites where a high proportion of the site interface is common. But where images need to be in a different color for specific sites.
Once you have the handler setup as above you can call it in two different ways:
/biochrome/alpha_ff0000_0000ff/picure.gif

Will take the file picture.gif and do an alpha map replacement using the colors ff0000 and 0000ff as the two ends of the spectrum. The use of alpha maps should be familiar to anyone who uses photoshop or gimp a lot. Essentially the colors are taken from the url and used as follows. The first color will be the background color of the image. The second color will be applied to those pixels where the red channel is turned on.

/biochrome/ff0000_00ff00_0000ff_ccffff/picure.gif

Will take the file and replace colors in the global color table with those provided on the url. In the example whatever color was the first in the color table will be replaced with red. Colors are replaced until we run out of replacements or positions in the color table to replace.

For further details of how to create your graphics and examples of using BioChrome see the examples directory or the Image::BioChrome documentation.

Apache::TestMB is a subclass of Module::Build to support Apache::Test.

SYNOPSIS

Standard process for building & installing modules:
perl Build.PL
./Build
./Build test
./Build install

Or, if youre on a platform (like DOS or Windows) that doesnt like the "./" notation, you can do this:

perl Build.PL
perl Build
perl Build test
perl Build install

This class subclasses Module::Build to add support for testing Apache integration with Apache::Test. It is broadly based on Apache::TestMM, and as such adds a number of build actions to a the Build script, while simplifying the process of creating Build.PL scripts.

Heres how to use Apache::TestMB in a Build.PL script:

use Module::Build;

my $build_pkg = eval { require Apache::TestMB }
? Apache::TestMB : Module::Build;

my $build = $build_pkg->new(
module_name => My::Module,
);
$build->create_build_script;

This is identical to how Module::Build is used. Not all target systems may have Apache::Test (and therefore Apache::TestMB installed, so we test for it to be installed, first. But otherwise, its use can be exactly the same. Consult the Module::Build documentation for more information on how to use it; Module::Build::Cookbook may be especially useful for those looking to migrate from ExtUtils::MakeMaker.

Apache::ASP is a Perl module for Active Server Pages for Apache with mod_perl .

SYNOPSIS

SetHandler perl-script
PerlModule Apache::ASP
PerlHandler Apache::ASP
PerlSetVar Global /tmp/asp

Apache::ASP provides an Active Server Pages port to the Apache Web Server with Perl scripting only, and enables developing of dynamic web applications with session management and embedded Perl code. There are also many powerful extensions, including XML taglibs, XSLT rendering, and new events not originally part of the ASP API!