Free apache 2.0 software for linux

mod_ziplook offers is a zip-file browsing module that can send files with gzip transfer-encoding.
Main features:
- Whole directory structure of ZIP-file can be seen.
- Separate files can be seen easily (/xxxx.zip/dir/afile.html)
- In case of directories index.html is looked. (/y/x.zip/dir/ => /y/x.zip/dir/index.html)
- Handles If-Modified-Since and NotModified-status
- If your browser supports gzip content-encoding and documents in ZIP-archive are "Deflate"-compressed: module changes files to gzip format in fly. This makes things very fast (and server cpu & network capasity is saved)
Module uses miniunzip - unzip library and that uses zlib.

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::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!

Apache::MP3 is a Perl module that can generate streamable directories of MP3 and Ogg Vorbis files.

SYNOPSIS

# httpd.conf or srm.conf
AddType audio/mpeg mp3 MP3
AddType audio/playlist m3u M3U
AddType audio/x-scpls pls PLS
AddType application/x-ogg ogg OGG

# httpd.conf or access.conf
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3
< /Location >

# Or use the Apache::MP3::Sorted subclass to get sortable directory listings
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Sorted
< /Location >

# Or use the Apache::MP3::Playlist subclass to get persistent playlists
< Location /songs >
SetHandler perl-script
PerlHandler Apache::MP3::Playlist
< /Location >
A demo version can be browsed at http://www.modperl.com/Songs/.

This module makes it possible to browse a directory hierarchy containing MP3, Ogg Vorbis, or Wav files, sort them on various fields, download them, stream them to an MP3 decoder like WinAmp, and construct playlists. The display is configurable and subclassable.

NOTE: This version of Apache::MP3 is substantially different from the pre-2.0 version described in The Perl Journal. Specifically, the format to use for HREF links has changed. See Linking for details.

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.

Gump is Apaches continuous integration tool. Apache Gump is written in python and fully supports Apache Ant, Apache Maven and other build tools. Gump is unique in that it builds and compiles software against the latest development versions of those projects. This allows gump to detect potentially incompatible changes to that software just a few hours after those changes are checked into the version control system. Notifications are sent to the project team as soon as such a change is detected, referencing more detailed reports available online.

You can set up and run Gump on your own machine and run it on your own projects, however it is currently most famous for building most of Apaches java-based projects and their dependencies (which constitutes several million lines of code split up into hundreds of projects). For this purpose, the gump project maintains its own dedicated server.

How does Gump work?

With Traditional Gump, project definitions are converted from XML to scripts native to the platform on which you are running. With Python Gump the XML is mapped into in memory objects for processing. Scripts execute cvs or svn update commands for every module which contains a project being built, and invoke builds for each project in an order that ensures that dependencies are satisfied. Build outputs are processed and, if successful, dependent projects are then built on these outputs.

The commands use the actual build.xml files from the projects, but do not use the scripts or jar files checked into CVS/SVN. Instead, the CLASSPATH is set and properties are passed on the command line.

Note

Gump sets Ants build.sysclasspath to only and manages the system classpath:
To quote Ant: Only the system classpath is used and classpaths specified in build files, etc are ignored. This situation could be considered as the person running the build file knows more about the environment than the person writing the build file

The net effect is that every project is built every day with the latest version of every dependency - including the latest Ant, latest JUnit, latest XML parser.

The results are captured into html pages that largely are consistent with the style of the Jakarta project. An extensive amount of hypertext links are added to allow quick and easy navigation, and failures are color coded on the main build page.

A Perl script which is driven off of a naglist will optionally send e-mails to various newsgroups upon matching strings being found in the build output. This is typically used to alert developers of build failures.

Apache::Cache is a cache data accessible between Apache childrens.

SYNOPSIS

use Apache::Cache qw(:status);

my $cache = new Apache::Cache(default_expires_in=>"5 minutes");

# if the if the next line is called within 10 minutes, then this
# will return the cache value overwise, this will return undef and the
# status method will be equal to the constant EXPIRED (exported by Apache::Cache
# on demande via the :status tag)

# the next line try to get the data from the cache, if the data is stored in
# in the cache and if it not expired, then this return the data. Otherwise
# if data have never been store in the cache, or if its expired, this will
# return undef and the status() method will be equal to constant EXPIRED (exported
# by Apache::Cache on demand, via the :status tag)

my $value = $cache->get(Key);

if($cache->status eq EXPIRED)
{
# cant get the data from the cache, we will need to get it by the normal way
# (via database, from file...)
$value = get_my_data(Key); # here, the get_my_data() function is a function of your
# programe that generate a fresh value

# this data have to expires in 30 secondes
my $expires_in = 30 secondes;
$cache->set(Key => $value, $expires_in);
}
elsif($cache->status eq FAILURE)
{
# dont use cache, cache maybe busy by another child or something goes wrong
$value = get_my_data(Key);
}

This module allows you to cache data easily through shared memory. Whithin the framework of an apache/mod_perl use, this cache is accessible from any child process. The data validity is managed in the Cache::Cache model, but as well based on time than on size or number of keys.

Additionnally, you can implement a cache with Apache::Cache in your module without the risk of namespace clash because Apache::Cache is enclosed in the constructors packages caller (see Apache::SharedMem for more details).